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

No annotations are provided, so the description carries the full burden. It only says 'GET', implying read-only, but never explicitly states side effects, error behavior, authentication needs, or anything else. The description provides virtually no behavioral disclosure.

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 extremely short, but this is under-specification, not effective conciseness. It contains no useful information beyond the path, failing to earn its place as a helpful description.

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?

With an output schema present but not described, and a host of sibling tools, this description is completely inadequate. An agent cannot determine what this tool does, what it returns, or when to select it.

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 0% for receipt_id, and the description does not explain the parameter beyond its presence in the URL path. It adds no meaning beyond what the schema already shows (type string, required).

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?

The description is just the HTTP path 'GET /v1/inference/pinned/{receipt_id}', which essentially restates the tool name as a URL. It implies a retrieval operation but does not explain what 'pinned' means or what the resource represents, leaving the purpose vague and poorly differentiated from siblings like hydracept_pinned_bulk_get.

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?

There is no guidance on when to use this tool versus the many siblings (hydracept_pinned_bulk, hydracept_pinned_run, etc.). No context, no exclusions, no alternative suggestions.

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