Set Default Execution Profile

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

With no annotations, the description carries the full burden. It usefully discloses that the setting is persistent and affects future mutating tools, but omits whether an existing default is overwritten, whether auth is required, or what happens if the profile ID is invalid.

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 sentences, zero filler, with the action and scope front-loaded ahead of the value enumeration. Every clause 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 single-parameter setter with no output schema and no annotations, the description covers purpose, scope, and value syntax adequately. Only edge-case behavior (overwrite, invalid ID, persistence duration) is left unstated.

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 baseline is 3, but the description goes further by enumerating the three concrete profile ID forms (walletconnect, agent:<walletId>, agent-eoa:<walletId>) that the schema only gestures at. That is genuine added meaning beyond 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?

States a specific verb ('Store'), the resource ('default execution profile'), and the scope ('for future mutating WalletChan MCP tools'), which distinguishes it cleanly from the get/list/clear_default_execution_profile siblings. An agent knows exactly what state this mutates.

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 explains the valid profile values but never states when to prefer setting a persistent default versus passing a profile per call, nor whether this must precede other tool calls. Usage is implied rather than guided.

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