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

No annotations are present, so the description bears the full burden of explaining behavior. It discloses a signature-authenticated mutation and a membership prerequisite, but is silent on side effects (e.g., whether the old pass is invalidated), permissions, and failure behavior. This is a meaningful gap for a write operation.

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?

One compact sentence with no filler; the eligibility condition leads and the message-format pointer is parenthetically appended. The phrasing is a bit awkward, but the length is appropriate.

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 three-parameter, no-output-schema tool, the description gives the key invocation context: prerequisite, signature mechanism, and where to find the message format. It is still incomplete about the response and side effects, but enough to guide a first correct call.

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 only 33% (timestamp only), so the description must compensate. It does partially: it links address to the wallet and signature to a signature from that wallet, while timestamp's role ('the one signed') is already in the schema. It does not specify address or signature format beyond pointing to the terms.

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?

Describes the concrete outcome (a new pass) and the precise eligibility condition (wallet already holds a membership), which clearly sets it apart from the sibling tools. It lacks an explicit verb like 'recover' or 'issue', and doesn't state what happens to the previous pass, so it is not a 5.

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?

Establishes a clear when-to-use condition: the wallet must already hold a membership and must supply a signature. It points to the terms for the message format, but does not explicitly name alternative tools or state when not to use this operation.

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