calculate_moroccan_income_tax

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

No annotations are provided, so the description must cover behavioral aspects. It mentions using official DGI brackets and family deductions, which implies authoritative calculation. It also lists output fields. However, it does not disclose any side effects or authorization needs, but for a calculation tool, this is acceptable.

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: two sentences. The first sentence states the purpose and method, the second lists return fields and a reference to related tools. No superfluous 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 presence of an output schema (context indicates true), the description is fairly complete. It covers purpose, input, output, and related tools. It could briefly explain how dependents affect deductions, but the schema fills that gap.

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%, so baseline is 3. The description mentions family deductions and taxable income, which relates to the dependents parameter, but does not add significant detail beyond what the schema already provides.

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 calculates Moroccan income tax (IR) using DGI progressive brackets with family deductions. It specifies the tool's output structure, distinguishing it from numerous sibling tax calculators for other countries.

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 use for Moroccan income tax calculations. It does not explicitly state when to avoid or compare with alternatives, but the tool name and sibling context make it clear. Adding an explicit usage context would improve it.

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