tax_summary

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

No annotations are provided, so the description carries the full behavioral burden, and '(read-only)' is the only disclosure — it usefully signals no mutation but is thin. Nothing is said about what period is covered when from_date/to_date are null, how the snapshot is computed, or any prerequisites.

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 a four-word fragment with no wasted words and the read-only note is front-loaded. However, it errs toward under-specification rather than genuine efficiency, omitting the content needed to select and invoke the tool correctly.

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?

Although the tool is structurally simple (two optional date parameters, output schema present), the description is contextually incomplete: it sits among nine siblings including several financial summary tools, and nothing explains how tax_summary differs or what the date parameters govern. The name and the read-only parenthetical carry nearly all the weight.

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%, so the description must compensate for the undocumented to_date and from_date parameters, but it mentions neither. The names are self-explanatory and the schema marks them optional with null defaults, yet the description supplies no date-format expectations, inclusivity semantics, or effective defaults.

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 identifies the resource ('tax summary') and output form ('snapshot'), making it reasonably clear this is a retrieval/report tool. It lacks an explicit verb, and given nine siblings including other financial reports, it does minimal differentiating work on its own, though the subject 'tax' sets it apart topically.

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?

There is no guidance on when to use tax_summary versus sibling report tools such as profit_and_loss, balance_sheet, trial_balance, or bank_balances. An agent is left to infer the selection criteria from the tool name alone.

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