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

Annotations already declare readOnlyHint and openWorldHint, covering the safety profile. The description adds that results are merchandising cards with tier/openable/delayed flags, but does not disclose any other behavioral traits such as pagination, filtering behavior, or auth needs. No contradiction exists.

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, front-loaded sentence with no filler. It names the resource, output form, and key card attributes compactly, and every word contributes to the tool's meaning.

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 simple read-only list tool with an output schema and one optional boolean parameter, the description is nearly sufficient. It misses only an explicit mention of include_retired and a pointer to rayana_ai_portfolio for singular access.

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 0%, and the description never mentions include_retired or explains how it affects the returned shelf. The schema's title and default value carry the only meaning; the description adds no parameter-level guidance and may even imply all portfolios are always included.

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 the resource ('Rayana AI's broadcast model portfolios'), the scope ('full shelf'), and the output form ('merchandising cards' with tier/openable/delayed flags). It distinguishes itself from the singular sibling rayana_ai_portfolio through the plural 'portfolios', but lacks an explicit verb like 'list' or 'retrieve'.

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 phrase 'full shelf' implies this is the list-all tool compared to the singular rayana_ai_portfolio, but no explicit when-to-use guidance or alternative tool names are given. Usage context is only implied, not directly stated.

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