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

Adds substantial context beyond the annotations: exact request_id retry returns the original receipt, read state afterward, editing an enabled schedule reroutes to the next future occurrence, archived also disables, and the tickets:write permission requirement. These are real behavioral traits not derivable from readOnlyHint/idempotentHint alone.

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?

Front-loads the core action and packs scope, mutation states, scheduling, idempotency, and permission requirements into a tight paragraph with no filler sentences.

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 mutation with a nested object, no output schema, and thin annotations, it covers permissions, idempotency, and lifecycle transitions well. The one remaining gap is run/scheduling outcome specifics (e.g. capture generation timing), but it explicitly tells the agent to read current state afterward, which mitigates this.

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?

With 0% schema description coverage, the description carries the load and does so well: it explains project_id scope semantics, expected_revision's role as a concurrency guard, request_id recovery behavior, and enabled/archived effects. It does not clarify hour/minute/frequency interactions against timezone, so it is strong but not exhaustive.

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 precise verb ('Replace') and resource ('the full definition of an owned report schedule'), immediately distinguishing it from create_portfolio_schedule, get_portfolio_schedule, and list siblings. The 'full definition' phrase signals replacement rather than partial patch semantics.

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 conditional guidance: use enabled=false to pause, archived to archive, preserve project_id for project scope vs omission/null for portfolio scope. It stops short of naming explicit alternatives (e.g. versus create_portfolio_schedule) but the branch conditions are actionable.

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