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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, and the description reinforces this with the explicit 'It records nothing' plus the hand-off to the edit-page Verify action. It also discloses the three possible outcomes (found, missing, inconclusive), which the annotations do not convey. It does not discuss the external fetch/timeout behavior implied by openWorldHint.

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 sentences, front-loaded with the core action and its outcome set, followed by the important non-mutation caveat. Wording is a bit tangled ('on one of your Free listings' sites now') and could be tightened.

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 description needn't spell out return values, and it still usefully previews the found/missing/inconclusive results and the returned markup. For a one-parameter read-only check, the agent has enough to call it correctly; only external-site failure behavior is left implicit.

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 100% and the single slug parameter is documented in-schema with its source ('from my_listings'), so the baseline is 3. The description never mentions the slug or its format, adding nothing beyond the schema.

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 and object: it looks for the Neeed badge on one of the user's Free listing sites and answers found/missing/inconclusive. That is clearly distinct from siblings like fetch, my_listings, or update_listing, though it never names those siblings to sharpen the boundary. The typo 'Neeed' and the loose phrase 'one of your Free listings' sites' slightly blur an otherwise precise statement.

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?

The description gives real context: run it to check the badge now, and if you want the link made dofollow or a hidden listing restored, the maker presses Verify on the listing's edit page instead. It thus routes the agent away from expecting this tool to mutate anything. It stops short of explicitly contrasting with sibling tools like update_listing or fetch.

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