wallet_get_summary

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

No annotations exist, so the description must disclose behavioral traits. It only says 'via Dritan' without explaining read-only nature, permissions, or side effects. This leaves agents uncertain about safety and preconditions.

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?

Extremely concise at one sentence, but brevity sacrifices necessary detail. While front-loaded with purpose, it omits critical information about parameters and behavior.

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, no parameter docs, and no annotations, the description is severely incomplete. An agent cannot reliably use this tool without guessing the return shape or parameter format.

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?

The input schema has one required string parameter 'wallet', but the description provides no clarification about its meaning (e.g., address, ID, or name). With 0% schema description coverage, the agent must infer from context, which is insufficient.

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?

Clearly states the tool fetches a basic wallet summary, with verb and resource. However, 'basic wallet summary' is vague compared to more specific sibling tools like wallet_get_balance or wallet_get_holdings, which reduce uniqueness.

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. With many wallet-specific tools (e.g., wallet_get_balance, wallet_get_holdings), the description should clarify that this provides an overview, which it does not.

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