calculate_part_time

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

No annotations provided, so description bears full burden. It states the return format {percentage, prorata_salary} but does not disclose any behavioral traits like rounding, error handling, or constraints. It is adequate but not rich in behavioral detail.

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: first states purpose and return format, second refers to related tools. No fluff, front-loaded, efficient.

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 tool simplicity (3 params, 1 required) and presence of output schema, the description is fairly complete. It explains what is calculated and points to related calculators. For a simple calculation tool, it is above average.

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%, baseline is 3. The description adds minimal parameter semantics beyond schema; it focuses on outputs. It does not enhance understanding of parameters beyond what schema 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 part-time work percentage and optional pro-rata salary, with a specific verb 'Calculate' and resource 'part-time work percentage...'. However, it does not directly distinguish from the many sibling calculator tools except for a reference to list_bundles for related 'temps-rh' 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?

The description includes 'See list_bundles for related 'temps-rh' calculators,' which implies alternatives but does not explicitly state when to use this tool versus others or provide exclusion criteria. The guidance is indirect.

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