get_meeting_stats

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

No annotations are present, so the description carries the full burden. It discloses that the tool uses GetUserAvailability and counts expanded recurring instances, and describes the return format. However, it does not state whether the tool is read-only, any required permissions, or potential side effects.

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 concise with a clear purpose sentence followed by a brief implementation note and structured Args/Returns sections. The only minor issue is the implementation detail ('Uses GetUserAvailability') which may not be necessary, but it does not detract significantly.

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?

An output schema exists, so return values are covered. The description adequately explains the parameters, purpose, and a key behavioral aspect (counting recurring instances). However, it lacks information on limitations, error conditions, or performance, which would be helpful for a stats aggregation tool.

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?

The schema provides only titles and types with 0% description coverage. The description adds essential semantics: 'people' is a comma-separated list of names/emails, 'start_date' and 'end_date' are in YYYY-MM-DD format. This significantly clarifies usage 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 clearly states 'Get meeting count statistics for one or more people over a date range.' It uses a specific verb ('Get') and resource ('meeting count statistics'), and defines the scope. This distinguishes it from siblings like 'get_calendar_events' which returns raw events.

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?

No guidance is provided on when to use this tool versus alternatives such as 'get_calendar_events' or 'find_meeting_time'. The description mentions the underlying API (GetUserAvailability) but does not explain trade-offs or exclusions.

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