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

With annotations only covering the mutation/idempotency profile, the description carries the real behavioral load: auth requirement (per-user key), hard rate limit (3 requests per key per day), and the async execution model split between immediate spec fetch/parse and worker-pass probing. It also discloses the return value (a request id for get_request_status), which no output schema provides.

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 and scope, then the argument shape, then operational constraints and the return value — an efficient ordering with no filler. It is a dense single paragraph with nested parentheticals, which slightly taxes scanning but every clause carries information.

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-argument, no-output-schema queueing tool this is complete: it explains the input object's shape, the auth and quota envelope, the async lifecycle, and what to call next for the result. Nothing an agent needs in order to invoke it correctly is missing.

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 schema for the single `target` parameter is a freeform object pointing at repo examples, so the description is the only real specification: it enumerates name, spec_url (OpenAPI 3 document), category, include_paths, baseline (with the meaning 'valid values for required params per path'), optional_values, and server. This adds substantial semantics the schema does not carry.

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 resource (queues a public, read-only, credential-free API for probing) and names the sibling it hands off to (get_request_status). An agent can distinguish it from get_divergences, search_claims, and the version tools without opening any 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?

The description makes the context of use clear: request a probe target here, then poll with get_request_status, and the target must be a public, credential-free API (an implicit constraint that excludes private/authenticated ones). It stops short of explicitly naming when NOT to use it or naming an alternative request path.

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