get_scheduled_task

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

With no annotations provided, the description carries the burden of establishing side effects. 'Get' unambiguously signals a read-only retrieval with no mutation, which is sufficient for a trivial getter. It does not mention not-found behavior or response format, but this is a minor gap for such a simple operation.

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?

One short, front-loaded sentence with no filler, repetition, or unnecessary detail. Every word contributes to identifying the operation and its scope.

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 one-parameter getter, the description adequately covers the operation, the target resource, and how to select it. The return value is inferable from the resource type even without an output schema. Not-found behavior is not specified, but that is not essential for a simple fetch.

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?

The input schema already documents the only parameter at 100% coverage with 'Scheduled task id'. The description's 'by id' only restates what the schema provides and adds no additional format, constraints, or source guidance. Baseline 3 applies.

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 names the exact resource ('scheduled task'), the operation ('Get'), and the selection semantics ('single ... by id'). This clearly differentiates it from the sibling list_scheduled_tasks, which would be used for retrieving multiple 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 phrase 'a single scheduled task by id' makes the invocation context clear: use this when you have a specific id and need one task. It does not explicitly name list_scheduled_tasks as the alternative, but the sibling list makes the distinction easy to infer.

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