get_scheduled_task

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

The readOnlyHint annotation already indicates this is a safe read operation, and the description adds useful behavioral context by noting the response includes the prompt the task will send. It does not contradict annotations, though it does not mention not-found behavior or response format details.

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?

A single, tightly worded sentence that front-loads the action, resource, and key return detail. Every word contributes meaning, with no filler or redundancy.

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 simple read-one operation with one parameter and a readOnly annotation, the description is largely complete. It tells the agent what it reads and highlights the important return content. It could be more complete with error or not-found behavior, but this is not essential for basic correct invocation.

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 one required parameter, task_id, with no schema-level description coverage. The description's phrase 'by its id' provides minimal semantic reinforcement, but it does not elaborate on the expected format, source, or meaning of the id beyond what 'Task Id' already conveys.

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 states a specific verb ('Read'), a clear resource ('one scheduled task'), and a distinguishing detail ('by its id, including the prompt it will send'). This clearly differentiates it from list_scheduled_tasks, which lists tasks, and from create/update/delete operations on scheduled 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 the tool is for retrieving a single scheduled task when its id is known, but it does not explicitly state when to prefer this over list_scheduled_tasks or when not to use it. Usage context is reasonable but left to inference rather than stated.

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