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

Annotations already declare readOnlyHint=true, and the description adds meaningful behavioral context beyond that: it explains the tier-based authorization behavior and the error case where a Pro key cannot access Elite content. This is valuable information an agent needs before calling.

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 with no filler. The first sentence front-loads the tool's function and contents, and the second concisely covers the important authorization/error behavior.

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?

For a one-parameter, read-only tool with an output schema, the description covers purpose, contents, and a key error condition. It is slightly incomplete in not pointing to a sibling tool for discovering slugs, but this does not prevent correct invocation.

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 provides only a bare 'slug' string with 0% description coverage. The description compensates by tying the slug to a model portfolio and explaining that the slug carries a tier affecting access. It does not specify slug format or how to find valid slugs, but for a single conventional identifier this is a minor gap.

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 opens with 'One model portfolio's full detail' and enumerates specific contents: holdings, overlay legs, event feed, NAV series, and windowed returns. This clearly identifies a detail/retrieval tool for a single portfolio and distinguishes it from siblings like rayana_ai_portfolios.

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 singular framing and requirement of a slug make it clear this tool is for retrieving full detail on one specific portfolio, not for listing portfolios. The tier/error warning also gives useful selection context, though it does not explicitly name alternative tools such as rayana_ai_portfolios for listing available slugs.

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