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

Goes well beyond the annotations by disclosing the credit cost model ('1 credit, charged only when it returns') and real failure modes (Reddit removals only detected when Reddit lets the check through, otherwise the recorded link counts; X checked via embed endpoint). This is exactly the kind of external-dependency and cost context annotations cannot convey.

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?

Front-loaded with the core action, but the body is a single dense run-on sentence with nested parentheses that is hard to parse. Every clause carries information, yet the structure could be broken into clearer statements of purpose, cost, and exclusions.

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 no output schema, the description should describe what a verify returns. It hints at outcomes (PR state, page live, listing rel, post still up) but not the response shape or status values, leaving a gap for a check tool whose result is the whole point.

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 0% for the single actionId parameter, so the description must compensate. It implies actionId identifies 'one recorded action' tied to a 'recorded link', connecting it to record_action/shipped siblings, but never states the format or explicitly where to obtain the ID.

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 ('Check') and resource ('one recorded action from the outside') and enumerates the concrete things it can verify: a PR's state on GitHub, a live page naming the product, a listing's rel link, a post's liveness. This is distinguishable from siblings like index_status or check_content, though it never names them directly.

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?

Provides useful negative guidance — index requests and drafts cannot be verified, and Bing index requests route to bing_connect — but does not say when to prefer this over sibling checks such as check_content, landing_check, or index_status, leaving the agent to infer the boundary.

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