aiworkhub_manager_sdlc_outcome_metrics

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

Annotations already declare readOnlyHint=true, and 'READ-ONLY:' merely restates it. The only genuine additions are 'bounded' (implying a capped result set) and the provenance of the events, but neither is explained — no cap value, no aggregation window, no auth or cost context.

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 front-loaded sentence with zero filler; nothing is redundant. Its compactness is appropriate for a one-parameter tool, though brevity here shades into under-specification rather than crispness.

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 shape need not be explained, but the description still never says which outcome metrics are returned or over what window, which is the central question for an analytics tool. The single undocumented parameter is also unaddressed, leaving the definition thin.

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 0% for the single `limit` parameter and the description never mentions it; 'bounded' hints that a cap exists but gives no default, max, or effect. With low coverage the description was expected to compensate and does not.

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?

States a verb-like outcome ('bounded outcome metrics') and a data source ('canonical task/review events'), so the general intent is graspable. But 'outcome metrics' is undefined — no list of metrics or dimensions — and nothing distinguishes it from sibling analytics tools like aiworkhub_task_usage_report or aiworkhub_task_cost_ledger.

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?

No when-to-use guidance, no exclusions, and no named alternative. The agent must infer from the tool name alone whether this or a sibling report answers its question.

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