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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds meaningful context beyond that: a required auth scope, calendar edge-case disclosures, and the important caveat that current health is not immutable failure history.

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 front-loaded with the core read action and returned fields, then adds edge-case and health semantics efficiently. It is compact and mostly free of filler, though the calendar-disclosure sentence is somewhat dense.

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 one-parameter read tool with no output schema, the description adequately covers purpose, auth, returned fields, and interpretation caveats. It falls short on helping locate or understand schedule_id, but the annotations and schema carry the rest of the safety profile.

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 has 0% description coverage for schedule_id, so the parameter is undocumented in structured fields. The description does not compensate by explaining the ID's format, ownership constraints, or how to obtain it, leaving meaning largely to the parameter name alone.

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 clearly states a specific verb and resource: 'Read an owned report schedule', and goes on to list returned fields such as next UTC time, local timezone, and current capture health. It distinguishes itself implicitly from sibling list/update tools by being singular and ID-based, but it does not explicitly name an alternative sibling.

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 a prerequisite ('Requires tickets:read') but does not explicitly say when to use this tool instead of list_portfolio_schedules or update_portfolio_schedule. Usage is implied by the singular schedule_id and ownership language, leaving alternatives to inference.

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