Get Scheduled Task

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

The description 'Return' aligns with the readOnlyHint annotation, so no contradiction. However, it adds no extra behavioral context beyond what annotations already provide (e.g., what happens if the name does not exist).

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?

The description is a single sentence with no unnecessary words, achieving maximum conciseness while still conveying the essential purpose.

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?

Given the tool's low complexity (one parameter, output schema exists, read-only) and the presence of annotation, the description is largely complete. It could mention that the task must exist, but the output schema likely covers return structure.

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?

With 0% schema description coverage, the description partially compensates by stating 'by name', indicating the parameter is the identifier. However, it lacks details on format or constraints, which is acceptable for a simple string parameter.

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?

The description clearly states the action 'Return' and the resource 'scheduled task', with the qualifier 'by name'. This distinguishes it from sibling tools like scheduled_tasks_list which returns all tasks.

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?

The description implies use when you need a single task by name, but it does not provide explicit guidance on when to use versus alternatives like scheduled_tasks_list, nor does it mention prerequisites or error cases.

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