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

The readOnlyHint annotation already indicates a safe read operation, so the description does not need to repeat that. It adds a little context with 'signed' and 'universal', but discloses nothing about return format, error behavior, or any operational constraints. This is acceptable for a zero-parameter read-only retrieval but adds only marginal behavioral insight.

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 description is a single concise sentence with no filler. Every word adds specificity to the resource being retrieved, and it is immediately clear what the tool returns. It is appropriately sized for a parameterless retrieval.

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?

Given no parameters, no output schema, and annotations covering the safety profile, the description is mostly complete for a simple retrieval. The only notable gap is lack of distinction from sibling tools like verify_portable_bundle, which an agent may need for correct tool selection.

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 tool has zero parameters, so the schema fully covers parameter semantics and the description has no additional burden. Per the baseline for zero-parameter tools, this scores well.

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 ('Retrieve') and identifies a concrete resource ('the universal signed Wever Pay connection bundle'). It goes beyond the title by adding 'universal signed' and 'Wever Pay', but it does not explicitly distinguish itself from sibling tools such as verify_portable_bundle or generate_client_configuration.

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?

There is no guidance on when to use this tool compared to related sibling tools, nor any mention of alternatives, prerequisites, or context where this bundle should be retrieved. The description only states what it does, not when to choose it.

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