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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond annotations: availability is a 'snapshot, never a reservation', times include configured schedule plus reservations plus connected-calendar busy periods, and it 'Requires the owned calendar service; never assume a timezone or invent a service name' - a real precondition.

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?

Front-loads the purpose and the discovery workflow, then layers snapshot semantics and sibling routing. Dense and mostly earning its place, though it runs long and could tighten the redundant 'creates no room, booking, invite or email' enumeration already implied by the read-only annotation.

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?

No output schema, but the description hints at what availability contains (configured schedule, reservations, connected-calendar busy periods) and covers the precondition and snapshot caveat. Adequate for a 4-param read tool; only the locale param's role is unaddressed.

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 carry the load. It explains the date/service/resource interaction and the meaning of an 'optional returned resource', but never mentions the locale parameter nor the date format. Baseline for a 0%-coverage schema sits at 3 because compensation is partial.

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?

States a specific verb and resource: reading the business's bookable calendar services, resources and host timezone, or checking available times on one local date. It clearly distinguishes itself from get_meeting/list_meetings (existing rooms) and prepare_meeting_link (reservation), so an agent can tell it apart from siblings without opening schemas.

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?

Explicitly prescribes the two-phase workflow ('Omit date/service/resource to discover options first; then provide both date and the exact service name') and names the alternative tools and when to use them ('Use list_meetings/get_meeting to find existing rooms separately'). Both when-to-use and exclusions are covered.

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