calculate_child_support

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

No annotations provided, so description bears full burden. It discloses the return structure ({income, rate_pct, monthly_support, annual_support}) and implies a legal basis, but lacks details on assumptions, accuracy, or side effects. Adequate for a simple estimation tool.

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: first states purpose, second lists return fields and a reference to related tools. No wasted words, front-loaded.

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?

Covers all key aspects: inputs, outputs, and a pointer to related calculators. Could clarify what 'rate_pct' represents, but overall adequate given the tool's simplicity and schema richness.

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. Description mentions the three parameters but adds no extra meaning beyond what the schema already provides (e.g., income is net monthly, children count 1-6, custody enum with French labels).

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?

Clearly states it estimates French child support (pension alimentaire) based on income, custody, and number of children. Distinguishes from siblings by specifying 'French' and referencing 'finance-france' calculators.

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?

Provides a hint to use 'list_bundles' for related calculators, but does not explicitly state when to use this tool vs. alternatives or any prerequisites. With many French finance siblings, more guidance would help.

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