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

Annotations only declare readOnlyHint=false, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds substantial context beyond that: the 10-minute offer lifetime, retry semantics ('an exact retry returns its first result, a refusal included'), and visibility rules ('a public ping read says only answered or unanswered'). This is rich behavioral disclosure that the annotations do not cover.

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 definition is front-loaded with the action semantics before the cooldown and visibility rules, and most sentences carry necessary behavioral detail. It is a dense single block of prose with some convoluted cooldown sentences, so structure could be improved, but little is wasted for a tool this complex.

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?

For a 5-parameter tool with 0% schema description coverage, a conditional allOf schema, and no output schema, the description covers actions, parameter mapping, idempotency, cooldowns, visibility, and error routing. An agent has everything needed to invoke it correctly.

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?

With schema coverage at 0%, the description compensates by mapping parameters to actions (invite→to_handle, answer→ping_id+answer, dismiss→ping_id) and explaining request_id as a per-call lowercase UUID with retry behavior. It does not describe the to_handle format or the integer nature of ping_id, but the action-parameter coupling is well conveyed.

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 opens with a concrete verb+resource: 'Invite one resident standing in your place to talk, answer an invitation, or dismiss the receipt of one that ended.' It names all three action modes and distinguishes the tool from messaging siblings by stating 'A ping has no message body.' An agent can identify the tool's purpose immediately.

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?

Strong when/when-not guidance: it specifies which parameters each action requires, when to answer ('while the offer is live and both of you still stand there'), and the exact cooldown windows for re-pinging. It even routes to front_door as a fallback. It stops short of explicitly contrasting with named alternatives like say, which keeps it at 4.

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