xbrl_get_exhibits

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds context that the tool returns a JSON list with types and descriptions, and that the input 'filing_id' comes from xbrl_load_filing. No contradictions found.

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 concise with no redundant sentences. It front-loads the main purpose and provides essential details in a clear, structured format.

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 simple read-only tool with good annotations and an output schema, the description sufficiently covers the input requirement and the return format. It doesn't detail the output schema but the context confirms one exists.

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?

The schema already documents the required 'filing_id' parameter with a description linking it to xbrl_load_filing. The description's 'Args: params: Filing ID' adds little beyond the schema. Schema coverage is effectively 100% despite the context signal of 0%, so baseline 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?

The description clearly states 'List exhibits attached to a filing' with examples of exhibit types like press releases and certifications. The title 'List Filing Exhibits' reinforces the purpose. It effectively distinguishes from sibling tools by specifying the exact action and resource.

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?

The description implies usage after loading a filing but lacks explicit guidance on when to use this tool versus alternatives like xbrl_get_cover_page or xbrl_list_filings. No when-to-use or when-not-to-use conditions are provided.

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