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

Annotations already cover readOnly/idempotent/non-destructive/closed-world, lowering the bar. The description still adds real context beyond them: 'immutable' revisions, inclusion of paused/archived schedules, newest-first ordering, and the required 'tickets:read' scope, which is genuine auth information an agent cannot get from the annotations.

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?

Four tight clauses with no filler, and the resource scope, ordering, pagination, side-effect statement, and required scope are all front-loaded in that priority order. Nothing is redundant with the schema or annotations.

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 no output schema, the description usefully discloses the return ordering and pagination fields (has_more, next_before_revision) plus the required permission. The remaining gap is parameter-level detail (limit bounds, cursor semantics) that neither the schema nor the description clarifies.

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%, so the description carries the load. It explains the ordering and gives a pagination protocol ('follow next_before_revision while has_more'), but it never explains the `limit` default/max or clarifies how the `before_revision` cursor parameter relates to the mentioned 'next_before_revision' response field, leaving a naming ambiguity.

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?

States a specific verb and resource ('Read immutable definition revisions of one owned report schedule') and scopes it with 'including paused or archived schedules.' The line 'No capture or state change' implicitly distinguishes it from the sibling list_portfolio_schedule_captures, so an agent can route correctly without opening either schema.

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 clear context: read-only inspection of a single owned schedule's history, covering paused and archived schedules. It steers away from capture-related tools via 'No capture or state change' but never names the alternative tool or states an explicit when-not condition, so it falls short of a 5.

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