qobrix_get_task

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

With no annotations, the description carries the full burden. It discloses the return shape ('{ data: { id, ... } }') and explains the meaning of several include options, which is valuable behavioral context. The verb 'Get' implies a read operation, though it doesn't discuss error handling or auth requirements. This is strong for a simple get tool.

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 sentences, front-loaded with the core purpose, and efficiently lists include options with parenthetical clarifications. No redundant or vague content.

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?

Given the tool's simplicity (2 params, no output schema), the description covers the essential details: purpose, return envelope, and include associations. It could mention potential absence behavior or typical use cases, but it is reasonably complete for a get-by-id 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?

The schema already provides 100% coverage for both parameters, so baseline is 3. The description adds beyond that by parenthetically explaining the semantics of include options (e.g., 'AssignedToUsers (who)'), which enriches understanding. It doesn't explain every option (e.g., CreatedByUsers) but adds meaningful value.

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 'Get a single task by UUID', a specific verb+resource combination. It also provides context ('task detail for pipeline management and follow-up audit') and implicitly distinguishes from sibling list/search tools which return multiple 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?

The description implies usage when a specific task UUID is known, and mentions pipeline management and follow-up audit as use cases. However, it does not explicitly name alternatives (e.g., qobrix_list_tasks) or state when-not-to-use, so it falls short of a 5.

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