irs-taxpayer-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool outputs a 'report with actionable findings' but does not specify whether this is a read-only analysis, if it requires authentication, its rate limits, or how it handles missing data. For a tool with 20 parameters and no annotations, this leaves significant behavioral gaps.

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 front-loaded with the core purpose ('One-click tax health check') and efficiently details the analysis scope in a single sentence. However, it could be slightly more structured by separating the output format from the analysis areas for better readability.

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 high complexity (20 parameters, no output schema, no annotations), the description is incomplete. It lacks details on parameter meanings, behavioral traits (e.g., data privacy, execution time), and output specifics, making it inadequate for guiding an agent through such a parameter-rich tool.

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 description coverage is only 5% (1 out of 20 parameters has a description), so the description must compensate but does not. It lists analysis areas like 'missed credits' and 'deduction optimization' but does not explain how these relate to specific parameters (e.g., 'charitableDonations' or 'retirement401k'), leaving most parameters semantically unclear beyond their schema types.

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 tool's purpose with a specific verb ('Analyzes') and resource ('your full financial picture'), and distinguishes it from siblings by emphasizing its comprehensive 'one-click' nature covering multiple tax aspects like credits, deductions, audit risk, and planning tips, unlike more focused sibling tools (e.g., 'analyze_education_tax_benefits' or 'calculate_federal_tax').

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 provides no explicit guidance on when to use this tool versus alternatives among the many sibling tools (e.g., 'generate_full_tax_report' or 'assess_audit_risk'), nor does it mention prerequisites or exclusions. It implies usage for a broad tax analysis but lacks comparative context.

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