tax_summary

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds only 'informational' and 'not accounting advice', which aligns with annotations but doesn't disclose additional behavioral traits such as data freshness, pagination, or rate limits. No contradiction.

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?

Extremely concise single sentence. Front-loads purpose and includes a critical disclaimer. No wasted words.

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 has 4 parameters, no descriptions, and many sibling tools, the description is too minimal. It doesn't explain return value shape (though output schema exists), date format expectations, or how direction/limit affect results.

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 0%, and the description only vaguely references 'for a period', hinting at fromDate/toDate but not explaining direction or limit. No additional meaning beyond parameter names.

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 it returns an informational tax summary for a period, with a disclaimer that it's not accounting advice. This gives a good sense of the tool's purpose, though it doesn't explicitly differentiate from sibling tools like tax_breakdown_report or vat_summary.

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?

No guidance on when to use this tool over alternatives. The description only mentions 'not accounting advice', which is a disclaimer but not usage context. Sibling tools like aruba_tax_breakdown_report and vat_summary exist, but no comparison is provided.

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