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

Annotations declare readOnlyHint=false and openWorldHint=true, and the description goes beyond them by disclosing the actual state change: a free listing with the badge becomes dofollow. It does not describe the negative outcome (what happens if no badge is found) or the response, which keeps it below a 5.

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 sentences, front-loaded with the action and followed by the consequence. No filler or restated metadata.

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 one-parameter mutation with no output schema, the description covers the action and its benefit but omits the failure path (badge absent, site unreachable) and says nothing about what the call returns, which the agent needs to interpret the outcome.

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% for the single url parameter, so the description must carry the meaning. "The listed site" does imply the url refers to an already-listed site rather than a listing ID and that a prior listing must exist, but no format, domain-vs-page, or required-state guidance is given.

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?

"Re-check the listed site for a link to curlship.com" gives a concrete verb (re-check) and resource (site membership/badge link) plus the downstream effect (free listing becomes dofollow). It is specific enough to distinguish from submit_listing or list_listings, though it does not explicitly differentiate itself from the similarly-named sibling refresh_listing.

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: call this after a listing is placed to confirm the badge and obtain the dofollow upgrade. There is no explicit when-not condition and no mention of the closest alternative, refresh_listing, leaving the agent to infer which of the two to invoke.

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