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

Annotations flag readOnlyHint=false and openWorldHint=true, and the schema exposes max_sats ("Most this call may charge"), indicating this is a paid, non-read-only network call. The description says nothing about cost, billing, or external fetching behavior — a meaningful omission given the payment semantics. It adds no behavioral context beyond what annotations and schema already show.

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?

Two short sentences with the core action front-loaded and zero filler. Appropriately sized, though the second sentence largely duplicates schema content rather than using the space for missing context.

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?

An output schema exists so return values needn't be described, but for a 5-parameter tool with payment semantics and an open-world network call, the description is too thin. It omits what happens on failure, fetch/timeout behavior, and cost implications — gaps the schema and annotations don't fully close.

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 both the log/url choice and the kind enum are already documented. The description only echoes the log-or-url alternative already stated in the schema, adding no meaning beyond it. Baseline 3 applies when the schema does the heavy lifting.

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?

Uses a specific verb+resource ("Shrink a failed CI log") that an agent can immediately parse. No sibling tool overlaps with this function (siblings are payment, catalog, and content-read tools), so differentiation isn't an issue, but there's nothing explicitly routing away from alternatives either.

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?

"Pass a GitHub Actions job link or the pasted log" gives input guidance and implies the tool is for failed CI logs, but it never states when to use this versus not, or any prerequisites. Usage context is inferred rather than stated.

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