xbrl_export_csv

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds that it returns a CSV string and allows customizable columns, which is useful behavioral context beyond the annotations.

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 (three sentences) and front-loads the purpose. However, the args line is somewhat vague (e.g., 'filters' not directly matching the schema's parameter names). Still efficient overall.

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?

The description mentions the output format and parameters, but it does not explicitly note that the filing_id comes from xbrl_load_filing or the default limits (max 5000 rows). Given the many siblings, more contextual details would improve completeness.

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 provides detailed descriptions for each parameter (e.g., 'The filing_id from xbrl_load_filing', 'Columns to include'). The tool description only lists parameter names without adding meaning beyond the schema, which already covers them well.

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 the verb 'Export', the resource 'facts', and the format 'CSV', distinguishing it from sibling tools like xbrl_export_json (JSON) and xbrl_export_concepts (concepts). The phrase 'for spreadsheet analysis' adds context.

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 when to use the tool (for spreadsheet analysis) but does not explicitly state when not to use it or name alternatives like xbrl_export_json or xbrl_export_concepts. Some context is provided, but exclusions are missing.

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