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

Annotations already declare readOnlyHint=false and idempotentHint=false, so the write/non-idempotent profile is covered. The description adds genuine behavioral context beyond that: no invitation delivery, and that the call returns the upcoming schedule. It stops short of stating permissions or duplicate-handling behavior.

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?

A single dense sentence with three clauses, each earning its place: scope, exclusion, limitation. The use condition is front-loaded ahead of the negative guidance.

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 an output schema present, the 'Returns the upcoming schedule' phrase is redundant but harmless, and annotations cover the safety profile. What an agent needs to call this correctly is present; only ambiguity in the undocumented notes/location params keeps it from a 5.

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 60% and the description adds only minor hints (an event needs a 'start time'). The start/end format details live in the schema, and notes/location are undocumented in both places, so the description does not compensate for the coverage gap. Baseline 3.

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+resource ('put a new event on their Xenition calendar') and enumerates the concrete event kinds it covers (meeting, call, deadline, reminder). It also names the sibling it is not, reschedule_event, so an agent can route correctly without opening either schema.

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?

Explicit when-to-use ('when the user wants to put a new event...'), explicit when-not ('Do not use to change an existing event'), and it names the alternative tool (reschedule_event). It also states a hard limitation (cannot send invitations), leaving nothing to inference.

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