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

readOnlyHint=true already covers the safety profile, so the bar is lower, and the description still adds real context: results are scoped to 'only the authenticated user's jobs' (an auth/isolation constraint not in the annotations) and it documents the naming conventions for workflow vs dataset schedules. It doesn't mention ordering, limits, or pagination, keeping it short of a 5.

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 purpose, then scope, then output shape, then naming, then cross-tool routing — a sensible order. Slightly padded by enumerating the returned fields, which the output schema already provides, but the remainder earns 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?

With an output schema present, the description needn't re-explain return values, yet it supplies the non-obvious parts — user scoping and the wf:/ds: naming scheme that an agent needs to interpret or act on the results. Nothing required to invoke this zero-parameter read 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?

Zero input parameters, so the baseline is 4; there is nothing for the description to disambiguate. The naming-convention detail (wf:/ds: prefixes) is useful but relates to interpreting results, not to inputs.

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 ('List the caller's scheduled tasks') and immediately ties it to the origin tool `schedule_task`, which disambiguates it from the many other list_* siblings. An agent can tell this apart from delete_scheduled_task and get_task_status 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?

Explicitly routes the agent onward: 'Use `name` as the key to remove a job with `delete_scheduled_task`', giving a concrete when-to-use-this-vs-sibling rule. It doesn't state exclusions or preconditions for the listing itself, but the listing scope is unambiguous.

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