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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful behavioral context by naming the full status vocabulary (Claimed, Pending with sub-states, Confirmed, Rejected, Reversed, Released, Expired), which tells the agent what states it can expect to encounter.

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 sentence that front-loads the scope ('every venue you have claimed or submitted') and then spends its remaining words on the status enumeration, which is the one detail that genuinely helps. No filler.

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 no-parameter, read-only listing tool with an output schema and readOnly/openWorld annotations, the description covers what is needed: what is listed and what statuses appear. Return shape is left to the output schema, which is appropriate.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing parameter-related for the description to compensate for. No syntax, filtering, or pagination options are mentioned, but none exist to document.

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 states a specific resource (venues) scoped to the caller's own claims and submissions, and enumerates the pipeline stages returned. That scope word 'you have claimed or submitted' is what separates it from advertiser.venues.list and ambassador.venues.suggestions without needing to open a 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?

Usage is implied rather than stated: it is clearly the 'see all my venues' call, but the description never says when to prefer it over ambassador.venues.suggestions, ambassador.venues.add/claim, or advertiser.venues.get, nor does it set any exclusions.

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