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

Annotations only declare the generic profile (readOnlyHint=false, idempotentHint=false, openWorldHint=true, destructiveHint=false). The description adds real operational context: execution is non-retrying, a successful run is metered against the monthly quota, the return is a status code plus response body, and one-time schedules are consumed by the call. These are exactly the facts an agent cannot infer 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?

Three short sentences with the core action front-loaded, followed by quota and lifecycle consequences. Nothing is repeated from the schema and no sentence is filler.

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 one parameter, no output schema, and only generic annotations, the description supplies the missing pieces: no retries, quota consumption, the shape of the result, and the one-time consumption behavior. An agent has everything needed to invoke it and predict the consequences.

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 coverage is 100% and the single 'id' parameter already documents its format and where to obtain it (schedule_request or list_schedules). The description adds no further meaning about the identifier, so the baseline of 3 applies.

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 states a specific verb and resource — send a scheduled request immediately, one time — plus modifiers (no retries) that separate it from siblings like schedule_request, pause_schedule, or resume_schedule. An agent can identify the operation without opening the 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?

The framing 'Send a scheduled request once, right now' plus 'A one-time request is finished after this' tells the agent this triggers an existing schedule rather than creating one. It stops short of explicitly naming alternatives such as schedule_request or delete_schedule or stating when not to use it.

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