Delimit Obs Logs

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description explicitly states 'read-only on the log backend' and 'no data is written, no ledger entry, no notification,' but the annotations set readOnlyHint to false. This is a direct annotation contradiction, so the score must be 1 despite the otherwise strong behavioral detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but well-structured with labeled sections: when to use, when not to use, sibling contrast, side effects, and prerequisite. Each section adds distinct information, and the core purpose is front-loaded in the first sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers prerequisites, license-gating behavior, failure payloads, internal backend routing, side-effect profile, and use-case constraints. An output schema is present, so return-value details are not required. The only significant flaw is the annotation contradiction, which is scored separately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds useful semantic context beyond the schema by giving example query values (error string, trace id, user id, request id) and clarifying that the search happens over a time window across configured sources.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Search application and system logs across configured sources (Pro).' It also explicitly contrasts itself with delimit_obs_metrics, which returns numeric series, making the tool distinguishable from many siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a detailed 'When to use' section with concrete symptoms such as error strings, trace IDs, user IDs, and request IDs, plus a 'When NOT to use' section naming delimit_obs_metrics, delimit_obs_status, and delimit_obs_alerts. It even warns against using it as a streaming/tail-follow surface.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.