Parse Form 26AS (text export)

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

Description clarifies read-only operation (parse file), consistent with readOnlyHint annotation. Adds output structure details but no mention of error handling or size limits. No contradiction with 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?

Two sentences, no waste. First sentence states purpose; second provides actionable usage instructions. Well-structured and front-loaded.

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?

Covers input, output items, and constraints (supported format, password). Lacks explicit output schema but mentions key fields. Adequate for a simple tool with one parameter.

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 is 100% for the single 'path' parameter. Description adds no additional parameter-level information beyond the schema's description.

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?

Specific verb 'parse' and resource 'Form 26AS TEXT export', with clear output items (deductor, TAN, section, amounts, totals). Distinguishes from PDF exports and implicitly from sibling 'parse_ais' by file type.

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?

Explicitly tells user to download Text format, notes no password needed, and states PDF is not supported. Provides context on reliability. Missing direct comparison to sibling tools.

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