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

Annotations already establish read-only, non-destructive, closed-world behavior, so the bar is lower. The description goes further by disclosing the returned fields, including how paused state surfaces as 'enabled: false' — signaling the actual response shape in the absence of an output schema.

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, zero filler, and the payload contents are front-loaded ahead of the dependency guidance. Every clause carries a distinct routing or content 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?

With no output schema, the description compensates by naming the returned fields, and it chains correctly to the create/update/delete/run_now siblings. Nothing an agent needs to call this correctly and thread the scheduleId forward is missing.

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 100%, so both flowId and workspace are already documented in the schema (flowId's provenance, workspace's auth caveats). The description adds no parameter-level detail beyond implying a single flow, which is the expected baseline when the schema does the heavy lifting.

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+resource ('Every schedule on one flow') and enumerates the payload (cadence, paused state, next fire time, delivery, last run status), which distinguishes it cleanly from sibling schedule mutators. An agent knows exactly what it gets back without opening a 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 explicit when-to-use: read before workbench_flows_schedule to avoid creating a duplicate, and to obtain the scheduleId required by workbench_flows_schedules_update / _delete / _run_now. Alternatives and the condition selecting them are named outright.

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