wallet_get_performance

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

With no annotations, the description must fully disclose behavioral traits. It only mentions 'via Dritan,' implying external data but no details on read safety, mutability, or side effects. The agent cannot infer whether this is a read-only or expensive operation.

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?

The description is too brief to be effective. It is concise but lacks substance, failing to earn its place by providing necessary context. A single sentence can be concise and informative, but this one is not.

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 four parameters, no output schema, and no annotations, the description is woefully incomplete. It does not explain return values, parameter formats, or how to interpret the results.

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 description coverage is 0%, and the description adds no meaning to the four parameters (wallet, showHistoricPnL, holdingCheck, hideDetails). The agent must guess their semantics from the parameter names alone.

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 'Fetch wallet performance via Dritan,' but it does not define what 'performance' means (e.g., PnL, returns, metrics). Among siblings like wallet_get_performance_chart and wallet_get_summary, the tool's specific role is unclear.

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 is provided on when to use this tool versus alternatives such as wallet_get_performance_chart or wallet_get_summary. The agent receives no hints about context or prerequisites.

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