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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds two genuinely new behavioral facts beyond the structured data: the authorization requirement ('Maintainer only') and the public audit trail ('Every use is logged publicly'), which materially affect an agent's decision to call it.

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 short clauses with zero filler; the authorization constraint and audit warning are front-loaded where an agent will see them immediately.

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 two-parameter mutation with annotations covering reversibility and idempotency, the description supplies the missing auth and audit context. It does not cover failure behavior (e.g., what happens if listing_id is not a live listing), which is the remaining gap.

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 carries the burden, yet it says little beyond the names: 'pin or unpin' maps to the pinned boolean and 'one live listing' maps loosely to listing_id. It never explains that listing_id must reference an existing live listing or what range/format is valid, though the parameter names are fairly self-evident.

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 pair (pin/unpin) and resource (one live listing), with the 'Maintainer only' qualifier scoping who may call it. No sibling in the list performs pinning, so no explicit sibling differentiation is needed, but the description never says how listing_id relates to the read_listing/browse identifiers.

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?

'Maintainer only' implies when the tool is available, which is useful restriction context, but there is no guidance on when to pin versus unpin other than the boolean itself, and no alternatives or preconditions are named.

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