calculate_senegalese_income_tax

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

With no annotations provided, the description carries the burden. It accurately describes the calculation and output, but does not mention side effects, authentication needs, or constraints. It is a read-only calculation tool, which is appropriate.

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 concise with two sentences: the first covers purpose and output, the second directs to related tools. No redundant or unnecessary information.

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 simple nature of the tool (1 parameter, full schema coverage, output described), the description is largely complete. It covers purpose, method, output fields, and a helpful reference to related bundles.

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?

The single parameter 'annual_income_xof' is fully described in the schema. The description adds value by specifying that the tax uses 'progressive brackets' and that the income is in XOF, providing context beyond the schema.

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 verb 'Calculate', the resource 'Senegalese income tax (IRPP)', and the method 'using DGI progressive brackets in XOF'. It also lists the output fields, distinguishing it from sibling tools by referencing related bundles.

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 implies usage for calculating Senegalese income tax and mentions a related bundle for context, but does not explicitly state when to use this tool over alternatives or any prerequisites.

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