Connect AwardWallet

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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, but the description adds crucial operational context beyond those flags: the credential flow via a local page, that AwardWallet validates it, that it is saved locally, and critically that secrets must never be pasted into chat. This is exactly the kind of behavioral nuance annotations cannot carry.

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?

Three sentences, front-loaded with the core purpose, then the credential mechanism, then the usage trigger. Every clause carries actionable information with no repetition of name or schema fields.

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 no-required-param, single-enum tool with no output schema, the description covers purpose, side effects (local save, external validation), the security constraint (never in chat), and the trigger condition. Nothing essential is missing for correct invocation.

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 100%, so the api enum's meaning is already documented. The description still adds value by clarifying that the credentials can be an API key or username/password depending on API type (covering accountAccess's key vs. paid APIs' user/pass), which enriches understanding of the api parameter's role beyond the schema's terse phrasing.

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?

States a specific verb+resource ("Connects this server to the user's AwardWallet account") and immediately clarifies what it returns (a one-time link to a local credential-paste page). This distinguishes it clearly from sibling tools like get_status, which reports state rather than establishing credentials.

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?

Explicitly names triggering conditions: "Use it when get_status or another tool reports a missing or rejected key, or when the user wants to change it." This gives both when-to-use and a sibling reference (get_status) plus the alternative user intent (rotating a key).

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