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

Annotations already declare the non-read-only, idempotent, non-destructive, open-world profile, so the bar is lower; the description still adds real value by stating the created schedule is INACTIVE and that enabling paid runs is a separate step, plus the approved-quote prerequisite. It doesn't cover concurrency/idempotency-key behavior or what the caps actually govern.

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?

Two sentences, front-loaded with the core action and immediately followed by the disambiguating alternative. No filler or repetition of the name/title.

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?

An output schema exists so return values needn't be described, and purpose/routing are covered. But for a 7-required-parameter, nested-object mutation tool with zero schema descriptions, the meaning of the caps and the scheduling spec is left entirely to raw JSON Schema constraints, which is thin for correct invocation.

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% across 7 required parameters, so the description carries the full explanatory burden, yet it only loosely maps quoteId via 'approved quote'. Nothing explains runCap vs monthlyCap, the spec frequency/timezone/hour/weekday fields, or idempotencyKey, leaving most required inputs undocumented in both places.

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 ('Save an inactive recurring research schedule') plus its origin ('from an approved quote'), which pins down scope rather than restating the name. It explicitly separates itself from resume_research_schedule, so an agent can pick between the two 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?

It names one alternative (resume_research_schedule) and the condition that selects it ('to enable paid runs'), and implies the approved-quote prerequisite. However it offers no guidance relative to the other research siblings (start_research, quote_research, pause/cancel_research_schedule), so the routing picture is only partially complete.

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