get_scheduled_task_status

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

Annotations (readOnlyHint=true, destructiveHint=false) already indicate safe read operation. Description adds specific behavioral constraint that detailed=true only works for SYSTEM and CUSTOMER-level tasks, not DEVICE-level, and directs to parentId for navigation.

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?

Three sentences, highly efficient: purpose, default vs. detailed mode, critical warning. No filler, front-loaded with primary function.

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?

No output schema, but description clearly indicates return is aggregated status or per-device breakdown. Mentions task hierarchy and parentId navigation, sufficient for agent to invoke correctly.

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 coverage is 100%, but description enriches both parameters: 'detailed' explained as returning per-device breakdown, 'taskId' restricted to parent IDs for detailed mode. Adds meaning beyond schema descriptions.

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?

Clear verb+resource: 'Retrieve status for a given scheduled task.' Distinguishes from sibling 'get_scheduled_task' by focusing on status, and further differentiates aggregated vs. per-device modes.

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 states default behavior (aggregated) and option for detailed per-device status via 'detailed=true'. Provides critical warning about task ID level restrictions, guiding correct usage. Could mention alternatives but context is clear.

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