wallet_get_holdings_chart

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

With no annotations, the description carries the full burden. It indicates a read-like operation (build chart) but does not disclose any behavioral traits such as data source, error handling, or performance implications. The description is too sparse to inform safe invocation.

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 a single sentence that directly states the tool's purpose with no wasted words. It could be slightly improved by front-loading key details, but is efficient.

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 the absence of an output schema and the relatively complex nature (4 parameters, chart generation), the description should explain the markdown format, how parameters affect output, and any limitations. It only states the broad output type, leaving significant gaps for an agent to use correctly.

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 description does not elaborate on any parameters beyond what the schema provides. Only one parameter ('top') has a description in the schema; the description adds no additional meaning for 'wallet', 'width', or 'height'. Schema coverage is low (25%), and the description fails to compensate.

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 it builds an embeddable holdings allocation chart markdown from wallet holdings for inline rendering. It is specific about the output format and use case, though it does not explicitly differentiate from sibling tools like wallet_get_holdings or wallet_get_performance_chart.

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_holdings for raw data or other chart tools. There is no mention of prerequisites, exclusions, or context for selection.

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