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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered; the trailing "Read-only" largely repeats that. What the description adds beyond annotations is the default environment-binding behavior and the account-wide escape hatch, which is real behavioral context for an agent deciding how results are filtered.

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 core purpose and the field list, and it is compact overall. The standalone "Read-only." sentence is redundant with the annotations and is the one piece of text that does not earn its place.

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 need not be explained, yet the description still previews them. For a zero-required-parameter, single-enum list tool with full annotations, everything an agent needs to invoke it correctly is present.

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% and the single enum's meaning is fully documented in the schema, so the baseline is 3. The description restates the scope semantics (bound environment by default, "all" for everything) without adding format or side-effect detail beyond the schema.

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 (List) plus resource (account's scheduled agents / cron deployments), and it names the returned fields (schedule, status, next/last run, standalone vs workflow-deployed). An agent can distinguish this from create_agent, pause_agent, or list_workflows 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 clear context: results are scoped to the bound environment, and passing scope "all" widens to every environment. It does not explicitly name a sibling alternative or a when-not-to-use case, but the environment-scoping condition is stated plainly.

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