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

Annotations already declare read-only, idempotent, non-destructive, closed-world, so safety is covered. The description adds real value beyond that: the required scope 'tickets:read', the disclosure that coverage may be incomplete/ambiguous, and the caveat that scope history follows the delivery-group hierarchy rather than V3 project placement. Return format/freshness details are absent, keeping it below 5.

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?

Three information-dense sentences, front-loaded with the core purpose and followed by the distinguishing caveats. No filler, though the enumeration of content domains is long enough that the key differentiator ('not a planned timeline') arrives late.

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?

With no output schema, the description does the work of describing what is returned (completion, estimates, weekly flow, lead/cycle evidence, risks, throughput scenario, retained history) and states the auth requirement and coverage caveat. A mutation-free read tool is adequately covered; missing only parameter-range specifics.

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%, so the description must carry parameter meaning. It implies root_id ('one owned feature epic') and weeks ('weekly delivery flow'), but never states the weeks window range (1-26), what root_id format is expected, or whether weeks defaults. Partial compensation, baseline territory.

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?

Opens with a specific verb+resource ('Read one owned feature epic') and then enumerates the exact content domains (task completion, estimates, weekly flow, lead/cycle evidence, risks, throughput scenario) plus a separate retained-history view. It also explicitly separates itself from adjacent concepts with 'not V3 project placement' and 'not a planned timeline', so an agent can distinguish it from get_ticket_delivery_plan or get_delivery_timeline.

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?

Gives clear context for when this is the right call (per-epic delivery summary with scope history) and one explicit exclusion ('it is not a planned timeline'), which steers agents away from planning tools. It stops short of naming a concrete alternative tool to use instead, so it lacks the explicit when-not/alternative routing of a 5.

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