task_device_tasks__get_task

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered elsewhere. The description adds only the endpoint path and the history-routing note; it says nothing about what a task entity contains, pagination-free single-record semantics, or error behavior for unknown UUIDs.

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?

Two short sentences, front-loaded with the verb and resource, no filler. The endpoint restatement is mildly redundant with the annotation title but useful as a confirmation of the underlying call.

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?

There is no output schema, so the description should ideally hint at the shape of a task entity (status, target device, timestamps); it does not. It does provide the key sibling cross-reference, which partially compensates for a simple single-record lookup tool.

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 description coverage is 100% with only two parameters, and the description merely implies taskUuid through the path template without adding format or sourcing guidance. The 'fields' projection parameter is left entirely to the schema, so 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?

States a specific verb and resource ('Get the task entity') and echoes the endpoint path with the required UUID key, so the agent knows exactly what is fetched. The closing pointer to ListTaskRuns() distinguishes it from the history-oriented sibling, though it does not explicitly contrast with list_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?

Gives a concrete routing rule: fetch a single task here, call ListTaskRuns() when a complete run history is needed. No explicit when-not guidance or prerequisites (e.g., where to obtain taskUuid) are given, keeping it below a 5.

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