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

Annotations already declare readOnly, idempotent, non-destructive behavior, but the description adds material context beyond them: keys are kept on the local machine, and the resulting server can sign and pay (shield, private pay, x402, MPP, spending limits). The key-custody statement is a genuine security property an agent should know before recommending it. It still doesn't say what the response looks like (commands as text vs. executed install).

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 sentence, front-loaded with the core action ('Commands to install the local Gloam MCP server'). The parenthetical capability list (shield, private pay, x402, MPP, spending limits) reads as marketing rather than selection-relevant detail, but it is not enough to break the structure.

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 single-optional-parameter, read-only helper with full annotations and no output schema, the description covers what it produces, which clients it supports, and the security posture. The only real gap is clarifying that it returns commands rather than executing the install.

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% and the single enum parameter is fully described, so the baseline is 3. The description's client list loosely mirrors the enum but is incomplete (no 'gemini', no 'all'), so it neither adds reliable meaning nor compensates for anything missing.

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 concrete output — install commands for the local Gloam MCP server — and enumerates the target clients, which distinguishes it from siblings like gloam_info or gloam_create_payment_request. It is slightly ambiguous whether the tool performs an install or merely returns commands, and the name 'connect_full_agent' doesn't perfectly match 'commands to install'.

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 explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The reader must infer from 'Commands to install' that this is the onboarding/setup entry point rather than a runtime payment tool.

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