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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that access is scoped to a verified claim and that only editable metadata is returned, but says nothing about auth failure modes or what happens for unclaimed slugs; with a rich output schema, return-shape disclosure is not required.

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?

One front-loaded sentence states the action and scope, followed by a compact Args block. The Args section largely duplicates schema descriptions, which is mild redundancy but keeps the definition scannable.

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 read tool with full schema coverage, annotations, and an output schema, the description covers the claim prerequisite and where to obtain the slug. What remains missing is the choice between this and edit_owned_listing or get, a minor gap given the tool's simplicity.

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 coverage is 100% and both parameters are documented identically in the schema, so the description adds no meaning beyond it. The mention that slug comes 'from the verified claim's listings or directory search' is the one useful sourcing hint, keeping this at baseline rather than below.

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 verb and resource: reading editable metadata for a listing covered by a verified claim. It distinguishes itself from siblings like get and edit_owned_listing implicitly via 'editable metadata' and 'owned', but it never names an alternative tool explicitly.

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 by the prerequisite phrase 'covered by your verified claim', which tells the agent a claim must exist first, and the slug guidance points to the claim's listings or directory search as the source. However, there is no explicit when-to-use versus when-to-use-edit_owned_listing or get, leaving the boundary to inference.

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