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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds genuinely non-obvious behavior: the response carries deployment-level flags (schedulerArmed) and an org-level permission gate, and it is the authoritative source of externalId and SOP title. It also defines empty-result semantics, which annotations cannot convey.

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-loaded with the purpose, then usage sequencing, then behavioral notes. Every sentence contributes, though the middle sentence is dense and packs three separate ideas (identity, requirement, warning) into one long clause chain.

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?

There is no output schema, so the description must carry return-value meaning — and it does, naming the returned fields (processes, schedules, schedulerArmed, gate) plus the empty case. Nothing an agent needs in order to call this correctly 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?

The tool takes zero parameters, so the baseline is 4. The description correctly implies no filtering inputs are needed and instead explains where downstream parameter values (externalId, SOP title) must be obtained.

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?

Specific verb+resource: 'List this organization's processes (SOPs written on agent seats) together with any schedules already attached to them.' It distinguishes itself from the scheduling siblings (create_schedule, update_schedule, delete_schedule, run_process) by framing itself as the read/lookup step that feeds them.

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?

Explicit sequencing rule: 'Use this BEFORE creating, changing, or running a schedule,' plus a named reason (it is the only source of agent externalId and SOP title). It also gives an exclusion/edge case — 'if this returns nothing, the org has no processes to schedule yet' — and a directive not to guess identifiers.

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