get_refinement_readiness_report

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 default checks, the option to add 'description', and the scope parameter. However, it omits behavioral traits such as whether the tool can publish results (given the 'publish' parameter) or if it has side effects, leaving gaps in transparency.

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 one concise sentence that front-loads the main purpose, then adds key parameter details. Every clause adds value without redundancy or fluff.

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?

The tool has 13 parameters, no annotations, and no schema descriptions. The description only covers a small fraction of the parameter space and omits important context like the publish option and how it relates to sibling tools such as publish_confluence_page. This is inadequate for the tool's complexity.

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 0% description coverage, so the description must compensate. It only explains 'scope' and 'checks', while 11 other parameters (e.g., publish, board_id, page_title, include_confluence_storage) remain undocumented. This is insufficient for a tool with 13 parameters.

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 the tool produces a 'refinement readiness report' identifying stories missing estimates and DOR/DOD labels, plus a suggested attendee list. It is specific about the resource and differentiates from sibling tools like list_sprints and get_sprint_issues, which focus on different data.

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 clear context: it is a weekly report for refinement meetings, and it explains the two scope options ('backlog' or 'sprint'). However, it does not explicitly mention when not to use it or name alternative tools, so it lacks explicit exclusions.

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