calculate_belgian_donation

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

No annotations provided, so description bears full burden. It partially discloses behavior: returns tax due and effective rate. However, it mentions 'region' as an input which is missing from schema, creating confusion. Lacks details on auth, rate limits, or side effects.

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, directly stating purpose and usage. No unnecessary words. Could be slightly more structured with bullet points, but effective.

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?

Tool has 2 params and an output schema. Description mentions output fields (tax due, effective rate) and usage context. However, the region mismatch and lack of assumptions reduce completeness. Adequate for a simple calculator but with gaps.

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% with clear parameter descriptions. Description adds mention of 'region' which is not in schema, contradicting the input schema. This misalignment reduces clarity for parameter usage.

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 computes Belgian donation tax by region for estate planning, using verb 'Compute' and resource 'donation tax'. It distinguishes from sibling tools like calculate_inheritance_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 usage context ('Use for estate planning in Belgium') and suggests related tools via list_bundles. However, it does not explicitly contrast with alternatives or state when not to use it.

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