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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered structurally. The description adds real value beyond that: it enumerates the returned fields (id, name, instruction, cadence, delivery, enabled state, last-run outcome), which compensates for the absent output schema. It omits pagination and auth behavior, keeping it at a 4.

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 purpose followed by return fields and a usage note. Efficient with no filler, though the field enumeration is dense and could be slightly compressed.

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?

For a read-only single-parameter list tool with annotations covering safety, the description supplies everything needed: identity, return shape, and a pre-create dedupe reason. The field list substitutes well for the missing output schema.

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?

There is a single parameter (workspace) with 100% schema description coverage, so the schema already documents its semantics fully. The description adds nothing about parameter usage, so the baseline of 3 is appropriate.

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 (List) plus resource (zv1 routines) and immediately defines what a routine is: 'scheduled natural-language instructions run by zv1.' This lets an agent distinguish it from routines_create and routines_update 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?

Gives an explicit use condition tied to a sibling: 'Check this before creating a routine so you don't duplicate one that already exists.' That routes the agent clearly to the create flow. It doesn't state when-not to call it or mention routines_update, so it falls just short of the full rubric.

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