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

Goes beyond the read-only/idempotent annotations by disclosing non-obvious behavior: downtime coalesces to one current capture and historical counts are never fabricated, plus the pagination contract and which field downstream consumers open. These are genuine behavioral traits an agent could not infer from annotations or schema.

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?

Purpose is front-loaded and every clause carries information; nothing is filler. It is dense and slightly crammed (coalescing rules, pagination, and auth in rapid succession), which keeps it just short of 5.

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 list tool with no output schema and zero schema description coverage, the description compensates by naming returned fields, explaining the pagination loop, and stating the auth scope. Adequate to call the tool correctly, though the limit parameter remains unexplained.

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 coverage is 0%, so the description must carry parameter meaning. It conveys the pagination cursor semantics ('Follow next_before_id while has_more') which maps to before_id, and implies schedule_id via 'one owned report schedule', but never documents limit (default 20, max 100) or the before_id name itself.

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?

Specific verb ('Read ... captures') applied to a precise resource ('one owned report schedule') and lists the concrete fields returned (scheduled_for, captured_at, missed_count, snapshot_id). This cleanly distinguishes it from siblings like list_portfolio_schedules, list_portfolio_schedule_revisions, and list_portfolio_snapshots.

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?

Gives operational guidance: paginate via next_before_id while has_more, and consume snapshot_id for readers/exports. It also states the tickets:read prerequisite. It does not explicitly contrast when to prefer this over list_portfolio_snapshots, so it stops short of 5.

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