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

Annotations already provide readOnlyHint and openWorldHint, and the description adds meaningful behavior: it makes exactly one call, never pays or signs, and returns status, payment headers, and body. It does not cover error behavior or rate limits, but it adds solid context beyond the annotations.

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?

The definition is a single front-loaded sentence with no wasted wording. It quickly communicates the core action, the no-payment constraint, and the observable result.

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 simple one-shot unpaid endpoint probe, the description covers the no-payment behavior and return fields. However, it leaves gaps around how to supply the endpoint slug, body, and query, which matters despite partial schema coverage and no output schema.

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 description does not explain any of the three parameters, and the required slug parameter has no schema description. While body and query are described in the schema, the description does not compensate for the undocumented required slug.

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: call a listed endpoint once without payment and inspect status, payment headers, and body. It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as bazaar_check or bazaar_endpoint.

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 unpaid, one-shot context implies when to use this tool, but there are no explicit when-not conditions or comparisons to alternatives. An agent must infer that this is for probing an endpoint without payment rather than checking, listing, or registering endpoints.

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