sam_fetch_description

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

Describes output as plain text, but doesn't detail edge cases (e.g., empty results, error handling) or whether formatting is stripped. No annotations exist, so description carries full burden; it's adequate but not comprehensive.

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 sentences: first states action and output, second provides usage context. No redundancy, front-loaded, every sentence earns its place.

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?

For a low-complexity tool with one parameter and no output schema, the description covers purpose, output format, and usage context. Minor omission: no mention of behavior for invalid noticeId, but not critical.

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?

Single parameter 'noticeId' already well-described in schema as '32-char hex notice id'. Description adds no extra meaning. With 100% schema coverage, baseline score of 3 is appropriate.

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?

Clearly states it returns full description/RFP body text as plain text, explicitly distinguishes from sibling sam_get_opportunity by addressing when that tool returns a URL instead of inline body. The verb 'fetch description' and resource 'notice' are specific.

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 explicit context: 'Useful when sam_get_opportunity returned a description URL instead of inline body, or for an LLM-friendly text dump.' This clarifies when to use, though doesn't explicitly state when not to use or name alternatives beyond sam_get_opportunity.

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