get_task

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

With no annotations, the description carries the full burden and does disclose a meaningful behavior: returns null when no task matches the id. It also signals "full record" depth, but it omits any statement about read-only safety, side effects, or how branch/project scoping affects the lookup.

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 entire description is one concise, front-loaded sentence with no filler. It states the core outcome first and then the edge case, making it easy to parse quickly.

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 required id is documented in the schema and the null behavior is stated, while the output schema covers return values. The description lacks explicit routing to list-oriented siblings and any safety statement, but for a straightforward get-by-id tool this is nearly 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 description coverage is 100%, and the schema already documents id, branch, and project well. The description adds no additional parameter-level detail beyond tying the id to the null case, which is acceptable given the strong schema coverage.

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 identifies the resource as "One task's full record" and adds the specific null-if-not-found behavior, so the purpose is immediately clear. It implicitly distinguishes itself from sibling list tools by focusing on a single task, though it does not explicitly name an alternative.

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 description implies usage: call with an id to retrieve one task's full record. However, it gives no explicit when-to-use or when-not-to-use guidance, and no sibling alternatives are mentioned, leaving the agent to infer the choice between get_task and list_tasks.

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