get_change_tasks

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

There are no annotations, so the description carries the full burden. It only says 'Get all tasks' with no mention of pagination, ordering, return format, required permissions, or side effects. For a read operation with no annotation safety signals, this absence of behavioral disclosure is a significant gap.

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 brief (one sentence plus an explicit Args block), which is efficient. However, the Args section largely duplicates the schema without adding semantic value, so while structured, it does not fully earn its place. It is under-specified rather than minimally sufficient.

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?

Despite having an output schema and a single parameter, the description omits crucial context such as how tasks relate to changes, pagination behavior, or what fields are returned. The output schema may cover return values, but the tool's invocation context is not fully explained, making it incomplete for an agent to confidently select and use it.

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?

The schema has one required parameter (change_id) with 0% description coverage, so the description must add meaning. It merely restates 'The change ID', adding no information about the format, range, source, or relationship to changes. This does not aid the agent beyond what the schema already provides.

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 states 'Get all tasks associated with a change' with a specific verb and resource, clearly distinguishing it from siblings like get_change_by_id (which returns change details) and get_tickets (which may return tickets but not change tasks). However, it does not explicitly clarify whether 'tasks' refers to change-specific tasks or a broader concept, which is a minor gap.

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 provides no guidance on when to use this tool versus alternatives. It implies usage when you need tasks for a given change_id, but there are no explicit exclusions, prerequisites, or comparisons to sibling tools. This leaves the agent to infer context from the name alone.

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