google_wallet_pass

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

No annotations are supplied, so the description carries the full burden. It identifies a creation action and a confirm gate, but does not disclose permissions, side effects, reversibility, rate limits, or what happens when confirm is false.

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?

Two front-loaded sentences with no filler. Both sentences carry actionable information: what is created and the required parameter value.

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?

An output schema exists, so return-value explanation is appropriately omitted. For a one-parameter create tool the call basics are covered, but with no annotations the missing behavioral and alternative guidance leaves it somewhat incomplete.

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 single boolean parameter has 0% schema description coverage, and the description supplies the essential value constraint: confirm=true is required. It does not explain why confirm is needed or what false does, but it adds the critical meaning the schema lacks.

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 ('Create') and resource ('Google Wallet pass JWT') tied to the Cumulus card. It distinguishes the create action from the sibling google_wallet_pass_status by verb, though it does not explicitly name any sibling.

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?

It provides a precondition ('Needs confirm=true') but does not explain when to choose this tool over apple_wallet_pass, google_wallet_pass_status, or other wallet tools. Usage is implied by the create verb, but no exclusions or alternatives are given.

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