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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description's 'Checks whether' aligns with that read-only profile — no contradiction. The description adds genuine value beyond annotations by disclosing the operational criterion: the check is scoped to a 'verified delivery file bound to this server,' which clarifies the exact state being probed. It doesn't describe return shape, but for a safety-covered read operation the added criterion is meaningful context.

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?

A single front-loaded sentence with zero filler. Every element — the verb, the resource, and the verification criterion — earns its place, and the description reads naturally with no redundant phrasing.

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, read-only tool with safety annotations, the core check is stated, but the return value is never described: an agent doesn't know whether it receives a boolean, a status string, or a richer object. With no output schema present, the description should hint at the result shape. The missing return semantics and implicit parameter identity are the main gaps.

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%, so the description bears the burden. It partially compensates by naming the resource type (Stripe offer), making it inferable that the single 'id' parameter is the offer identifier, but it never explicitly states what id refers to, its format, or provenance. Since there is only one simple string parameter and the resource is named, this is adequate but not thorough — a baseline 3 is appropriate.

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 uses a specific verb (checks whether) with a clear resource (Stripe offer) and an outcome criterion (verified delivery file bound to this server). This distinguishes it from siblings like get_stripe_checkout_link and get_request_credit_links, since none of those reference delivery-file verification. It doesn't name a sibling explicitly, which prevents a 5, but the resource+criterion combination makes its purpose unambiguous.

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?

No guidance is given on when to use this tool versus alternatives. It doesn't state prerequisites (e.g., that an offer must already exist), exclusions, or conditions that would route an agent to a sibling like list_stripe_offers or get_stripe_checkout_link. The title 'Check fulfillment readiness' implies a follow-up-after-purchase context, but this is left to inference rather than stated.

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