find_meeting_time

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

Annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which the description does not contradict. The description adds context about parameter aliases and deprecation but does not disclose behavioral traits such as rate limits, authentication requirements, or response format. Given annotations cover safety, this is adequate but not exceptional.

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 two sentences long: the first succinctly states the purpose, and the second provides essential parameter guidance. No redundant or unnecessary information is present.

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?

Despite no output schema, the description does not describe the return format (e.g., an array of time slots). For a tool with 10 parameters, the description covers input aliases well but is incomplete for an agent to fully understand what the tool returns.

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 adds value by indicating preferred parameter names and deprecating slot_duration in favor of duration. This helps the agent choose between aliases and avoid deprecated fields.

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 the tool's purpose: 'Find time slots when multiple agents are all free simultaneously.' The verb 'find' and resource 'time slots' are specific, and 'multiple agents' differentiates it from sibling tools like get_availability, which returns availability for a single agent.

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 provides guidance on parameter usage, noting preferred names (agents/start/end) and aliases that match other APIs. However, it does not explicitly state when to use this tool over siblings like create_proposal or get_availability, and it lacks 'when not to use' directives.

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