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

Annotations already declare readOnly, idempotent, non-destructive and closedWorld, so safety is covered structurally. The description still adds value by disclosing what information is surfaced (native schedule state, remaining run/credit limits, next occurrence) and that the call does not resume the schedule — a side effect an agent might otherwise fear.

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?

A single front-loaded sentence with no filler; the most important distinction (read without resuming) lands at the end as a qualifier rather than buried in preamble. Nothing here could be cut without losing signal.

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?

The tool is simple — two identifiers, an output schema, and rich annotations — so the description only needs to state purpose and scope, which it does. The one visible gap is that neither identifier is explained, though that is minor against the supplied schema and output contract.

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% for both parameters, so the burden falls on the description, which never mentions workspace_id or schedule_id. The names are largely self-evident identifiers, but no guidance is given on format, source, or whether the schedule must belong to the given workspace.

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?

Names a specific verb and resource ('Read native schedule state') and enumerates what is exposed: state, remaining run/credit limits, and next occurrence. The closing clause 'without resuming it' implicitly separates it from activate_recurring_schedule and pause_recurring_schedule, though those siblings are never named.

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?

Usage is only implied: the 'without resuming it' phrase signals a peek-at-status operation rather than a mutation, which helps an agent choose it over activate/pause/revoke. There is no explicit statement of when to prefer it over list_recurring_recipes or when it is not appropriate.

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