show-task

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

With no annotations, the description must carry the behavioral disclosure burden. 'Get' strongly implies a read-only, non-mutating operation, and 'app-only' hints at access restrictions. Still, it does not clarify authentication requirements, error behavior, or what 'detailed information' includes, which is meaningful given there is no output schema.

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, front-loaded sentence with no filler. Every word contributes to either the operation, the target resource, or the usage context, and it is easy to scan.

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?

The tool is simple: one required parameter, fully described in the schema, and the description gives the purpose and app context. The lack of an output schema makes the return format ambiguous, but for a basic singular-task lookup the definition is reasonably complete.

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%, so the schema already documents taskId and its example format. The description adds little beyond 'specific task', which weakly maps to the taskId parameter but provides no additional meaning or usage details beyond the schema.

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 ('Get') and resource ('detailed information about a specific task'), making the tool's purpose unambiguous. It does not explicitly contrast itself with the sibling tools, but 'specific task' signals a singular lookup versus broader task visualization/polling.

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 'app-only, used by the visualization UI' provides contextual guidance about intended usage and implies it is not for general-purpose agent calls. However, it does not explicitly describe when to prefer show-task over poll-tasks or visualize-tasks, leaving some routing decision to inference.

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