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

Annotations already establish the safe read-only, idempotent, non-destructive profile. The description adds useful context with 'Simulated, not recommendations,' which is a meaningful behavioral caveat, but it does not discuss response format, refresh behavior, or other operational details.

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 two short sentences with no waste. The portfolio contents are front-loaded and the simulation disclaimer follows as a compact caveat.

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 one simple required parameter, full schema coverage, and read-only annotations, the remaining burden is to describe return content. The description enumerates the portfolio fields and adds a simulation caveat, making it sufficiently complete, though it does not detail output shape or freshness.

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 100%, and the single 'agent' parameter is fully documented in the schema as a slug with examples. The description adds no parameter-specific meaning beyond the schema, which fits the baseline of 3 when structured fields do the heavy lifting.

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 identifies a specific resource — one AI agent's paper portfolio — and enumerates the contents: holdings, cash, pending orders, and performance vs benchmarks. It is clearly distinct from activity or disagreement tools by content, though it does not explicitly contrast with siblings.

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?

The description gives no explicit guidance on when to use this tool versus alternatives such as get_agent_activity or get_agent_disagreements. Usage is implied only by the phrase 'paper portfolio,' with no exclusions or routing advice.

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