suggest_meeting_times

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

No annotations are provided, so the description must disclose behavior. It mentions combining busy windows and working-hours filtering, but fails to detail output format, time zone handling, error cases, or the effect of the limit parameter.

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 three concise sentences with no waste. It front-loads the primary purpose and adds relevant nuance about attendee omission.

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 8 parameters and no annotations, the description is incomplete. It covers high-level purpose but omits parameter details and output specifics. An output schema exists but its content is unknown, so description should still hint at return value.

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 0%, so the description must explain parameters. It clarifies attendees, window, and working hours generally, but does not explicitly describe duration_minutes, window_start, window_end, working_hours_start/end, account, or limit. Only attendees and the basic concept are addressed.

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 uses a specific verb 'Find time slots' and resource 'meeting times', clearly stating the function: find free slots for all listed attendees. It distinguishes from sibling tools like free_busy by aggregating busy information.

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 implies usage for scheduling by stating it combines busy windows and working hours filtering. It provides context for omitting attendees, but does not explicitly state when to use this tool versus alternatives or give exclusion criteria.

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