aiworkhub_manager_sdlc_case_for_task

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

readOnlyHint=true already tells the agent this is a safe read, so 'READ-ONLY:' is redundant. However, 'or a typed unknown' adds genuine behavioral information: missing data is returned as a typed sentinel rather than raised as an error. 'Bounded' also signals the payload is size-limited, though no bound is quantified.

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?

One short, front-loaded clause with no filler. The only cost is that its terseness comes partly from undefined jargon rather than from efficient compression.

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?

An output schema exists so return values needn't be explained, but the description is still inadequate for a tool sitting among several near-identical SDLC packet tools: no usage context, no differentiation, and no parameter format guidance despite 0% schema coverage.

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 single task_id parameter has 0% schema description coverage, so the description must carry the semantics. 'Bound to one canonical task' implies task_id is a canonical task identifier (not a case id), which is useful, but it never states the accepted format or where canonical task ids come from.

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 phrase 'bounded case packet bound to one canonical task' identifies the resource and its scoping, but there is no verb ('reads'/'fetches') and the terminology ('bounded case packet', 'typed unknown') is project jargon. It does not distinguish this from the very similar siblings aiworkhub_manager_sdlc_case_get or aiworkhub_manager_sdlc_stage_packet, so an agent must infer the difference.

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?

There is no when-to-use guidance, no prerequisites, and no naming of alternatives. With at least four sibling SDLC case/packet tools (case_get, case_create, case_create_for_task, stage_packet), the absence of any disambiguation is a real gap.

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