tasks_tasks_get

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

The description adds no behavioral context beyond what the name and annotations already convey. The readOnlyHint annotation covers the safety profile, but the description does not mention response shape, error behavior, or any prerequisites beyond the required parameters. With annotations shouldering the main load, this still provides no additional value.

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 sentence with no filler or repetition. It is front-loaded and every word is essential, making it an ideal example of conciseness for a simple getter tool.

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 has no output schema, and the description does not hint at what fields the returned task object contains or how errors (e.g., not found) are handled. While the parameters are fully defined, the lack of response information makes it incomplete for an agent that needs to consume the result.

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%: both 'task' and 'tasklist' are already described as 'Task ID' and 'Task list ID'. The description 'Get a task by ID' does not add further meaning or format details, so it meets the baseline for fully described parameters.

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 'Get a task by ID' states a specific verb and resource, clearly indicating this tool fetches a single task. It distinguishes itself from siblings like tasks_tasks_list (which lists tasks) and tasks_tasks_update (which modifies), so an agent can tell them apart.

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 'by ID' provides clear context that this tool is appropriate when a specific task identifier is known. While it doesn't explicitly name alternatives like tasks_tasks_list, the context is unambiguous and no exclusions are needed for such a simple operation.

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