Document metadata

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

Annotated readOnlyHint true, destructiveHint false, idempotentHint true, openWorldHint true. Description augments with: raw upstream fields in jurisdiction_data, 404 on synthesized IDs, 501 for unsupported jurisdictions, paywalled body on empty formats. No contradictions.

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?

Concise, well-structured: purpose first, then usage guidelines, then caveats. Every sentence adds value without redundancy.

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 3-param tool with output schema and annotations, description covers all critical aspects: purpose, inputs, usage flow, error conditions, and behavioral notes. No gaps.

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 coverage 100%, each parameter has description. Description reinforces document_id origin and jurisdiction support via list_jurisdictions. Adds meaning beyond schema with caveats and context.

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?

Explicitly states it retrieves metadata for a filing document by document_id from list_filings. Distinguishes from sibling fetch_document by advising to call this tool first when document may be large or format unknown.

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 clear when-to-use guidance: before fetch_document, when size or format uncertainty. Also gives explicit warnings: do not construct document_id, synthesized IDs will 404, empty formats indicate paywalled content, unsupported jurisdictions return 501.

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