xbrl_render_statement

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so no contradiction. The description adds that it uses the presentation linkbase and fills from instance data, but does not disclose error handling, data freshness, or output size constraints.

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 short and front-loaded with the key purpose. However, the Args/Returns section is somewhat redundant given the schema. Overall, it is efficient but not perfectly concise.

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?

Given the tool's moderate complexity and the presence of output schema (not shown but indicated), the description covers the main purpose, inputs, and output format. It could mention that the output is a formatted string, but it's sufficient for an agent to use correctly.

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 input schema already contains detailed descriptions for each parameter (e.g., statement type options, format). The tool's description merely repeats 'Filing ID, statement type, and format', adding no new semantic information beyond the schema. Schema coverage is effectively high, so baseline 3.

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 'Render financial statements' and lists specific types (balance sheet, income statement, etc.), making the purpose clear. However, it does not explicitly differentiate from sibling tools like xbrl_smart_summary or xbrl_financial_ratios, which may also produce financial data.

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 (mentioning 'filing_id' and 'presentation linkbase hierarchy'), but lacks explicit guidance on when to use this tool vs. other XBRL tools, or any prerequisites or limitations.

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