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

With no annotations, the description carries the full burden; it does disclose one real behavioral trait — that the output is advisory/interpretive and not financial advice — which is useful for framing. But it says nothing about permissions, auth, whether the score is cached or computed live, or latency, so it remains partial for a tool with zero annotation coverage.

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?

Two sentences, front-loaded with what the score is and what it contains, followed by the disclaimer. Every clause maps to something the agent needs (scale, components, non-advisory nature); minor redundancy in 'as shown in the app'.

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?

With no output schema, the description steps in and enumerates the score's constituent dimensions (diversification, mix, stablecoin reserve, performance, risk) alongside the 0–100 range, which is enough for an agent to interpret the return. It stops short of describing how the score is computed or what shape the response takes (single number vs per-dimension breakdown), a modest gap for a zero-parameter read tool.

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 tool takes no parameters (0 required, 0 optional), so there is nothing for the description to disambiguate; baseline 4 applies. The schema is trivially empty and the description correctly does not invent inputs.

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?

It names the specific resource (the user's portfolio score) and pins down the scale (0–100) plus the five dimensions that compose it, so an agent knows exactly what is returned. It does not, however, distinguish itself from the closely named sibling get_portfolio, leaving the agent to infer the difference.

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?

There is no statement of when to call this instead of get_portfolio or get_metrics, nor any prerequisite or context. The closing sentence is a liability disclaimer ('a reading aid, not a recommendation to buy or sell'), not usage guidance, so the agent gets no routing help.

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