calculate_cheque_repas

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

No annotations provided; description only mentions calculation and return values. Lacks disclosure of side effects, permissions, or constraints beyond schema.

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 concise sentences front-load key info: purpose and output. 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?

With output schema and 3 simple numeric parameters, description is adequate for a straightforward calculator. Would benefit from hinting at Belgian regulatory context.

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 describes all 3 parameters with defaults and constraints (100% coverage). Description adds no extra meaning beyond listing output fields. Baseline 3 is appropriate.

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?

Description specifies exact resource ('Belgian meal voucher (cheque-repas / maaltijdcheque) benefit') and verb ('Calculate') with explicit output fields, distinguishing it from siblings.

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?

Mentions related 'list_bundles' for other calculators but no explicit when-to-use or when-not-to-use guidance. Usage context is implied by tool name.

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