get_wallet_mode

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

Annotations are absent, so description alone must convey behavior. It discloses that it returns mode and address but fails to mention network dependency or whether a wallet must be active. Side effects are likely none, but network parameter's impact on results is implicit.

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?

Single sentence efficiently covers the core purpose. Very concise, though slightly more structure (e.g., listing outputs) could improve it. No wasted words.

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?

Given no output schema, description should hint at return format but does not. Lacks mention of prerequisites (e.g., wallet connection) or error conditions. Adequate for a simple read tool but not fully complete.

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 covers the parameter with description, so baseline is 3. Description implies the result depends on network, adding marginal value. Not enough to raise score above baseline.

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 clearly states the tool retrieves the current signing mode and active address, using specific verb 'Get' and resources 'signing mode' and 'active address'. It distinguishes from sibling tools like get_wallet_address (only address) and set_wallet_mode (setter).

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?

No guidance on when to use this tool versus alternatives (e.g., get_wallet_address, set_wallet_mode) or prerequisites such as needing a connected wallet. The description is purely declarative without usage context.

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