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

With no annotations, the description carries the full burden. It only hints at local signing and local record-saving behavior, but does not disclose prerequisites, side effects, required permissions, or what the setup entails. This is minimal for a setup tool that likely mutates local state.

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 short sentences deliver the essential alias relationship and usage context with no filler. The description is front-loaded and every word earns its place.

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 tool with 43 parameters, no annotations, and no output schema, this description is too sparse. It omits setup steps, required inputs, return values, and any behavioral details beyond the high-level flow. The alias reference helps but does not make the description self-sufficient.

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 only 33% across 43 parameters. The description does not compensate by explaining any parameters or how the gift-card flow maps to the schema. It adds no parameter-level meaning beyond what is already in the schema.

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 identifies the tool as an alias for setup_local_wallet_bridge and specifies a concrete use case: crypto-to-gift-card flows with local signing and saved receipts/gift-card records. This clearly indicates what the tool is for, though it relies on the alias relationship rather than stating an independent verb-resource action.

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 description explicitly says 'Use for crypto-to-gift-card flows where the user signs locally and wants receipts or gift-card records saved locally.' This gives clear when-to-use context, but it does not mention when not to use it or alternatives beyond the alias reference.

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