get_assets_breakdown

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

No annotations are provided, so the description must carry the burden. 'Get' implies a read-only operation, which is appropriate. However, it does not disclose potential behavioral traits like authentication needs, rate limits, or data volume. For a simple query tool, this is minimal but adequate.

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?

A single sentence of 11 words, no wasted text. The verb 'Get' is front-loaded, immediately conveying the action. Every word 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?

Given the tool has one required parameter with an enum, no output schema, and is a simple data retrieval, the description is complete. It answers what the tool does, what dimensions are available, and implies the output is a breakdown.

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 schema has 0% description coverage, but the description explicitly explains the single parameter 'dimension' by listing the enum values (protocol, network, asset). This adds full meaning beyond the schema, clarifying exactly what dimension breakdowns are available.

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 verb 'Get' and the resource 'Smart Allocator invested-asset breakdown', and specifies dimensions (protocol, network, asset). It distinguishes from sibling tools like get_protocol_overview or get_smart_allocator_overview by focusing on the breakdown by dimension.

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. The description does not mention prerequisites, when-not-to-use, or context such as requiring the Smart Allocator to be active. Siblings are listed but no differentiation provided.

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