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

Discloses write nature (proposing time, host notified), conditional auth requirements, and Turnstile token. No contradiction with annotations (readOnlyHint=false).

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 with the main action first, followed by necessary details on authentication and notification. No redundant information.

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?

Covers purpose, auth flow, callback (host notified), and conditional parameter. No output schema needed as effect is described. Sufficient for selection and invocation.

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?

Adds context to parameters: meetingId is for existing meeting, time parameters are unix timestamps, turnstileToken is for anonymous callers. Schema covers 67% with descriptions; description fills gaps and explains flow.

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?

Describes a specific action: proposing a different time for an existing meeting on behalf of a guest. Clearly distinguishes from sibling tools like create_meeting or find_common_slots.

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?

States when to use: to propose a new time. Provides context on authentication requirements and host notification. Does not explicitly exclude alternatives but is clear enough.

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