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

With all annotation hints false, the description carries the transparency burden. It discloses the returned shape and ranking behavior ('UTC instant with the local time for every participant and a fairness score, best first'), and the verbs 'Rank' and 'Returns' imply a read-only search, though it never explicitly states that no data is modified.

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, front-loaded with the core behavior and no filler. Every clause adds either the ranking rule or the return format.

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?

The description plus the exceptionally detailed input schema covers behavior, defaults, free-tier limits, and argument semantics. Since no output schema exists, the description's mention of UTC, local times, and fairness score provides the essential return-shape information.

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 description coverage is 100%, and the schema itself explains defaults, limits, and the fairness-score meaning, e.g., 'distance in hours from 13:00 local'. The description only mentions fairness at a high level and adds little 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 opens with a specific action ('Rank the times') and names the resource ('meeting slots') and constraint ('every participant is inside their own working hours'). It also states the return format (UTC instant, local times, fairness score), which distinguishes it from sibling tools like overlap or business_days.

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 gives no explicit when-to-use or alternative routing, such as naming a sibling to prefer in another case. The intended context is only implied by the tool's name and the 'every participant' phrasing, so an agent must infer when this beats the sibling tools.

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