list_stories

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

The description adds that stories are listed and filters are optional, which is consistent with annotations (readOnlyHint=true, openWorldHint=true). However, it does not disclose behavioral details like pagination or default ordering beyond what annotations indicate.

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 very brief and lacks structure. While concise, it could be slightly more informative without becoming verbose. Every sentence is earned, but there is room to add clarity.

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 simplicity of the tool and presence of annotations, the description adequately covers its purpose and filters. However, it omits details like pagination, sorting, and description of the return format, which would be helpful for a complete understanding.

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 coverage is 100%, so the schema already documents all parameters. The description adds minimal extra meaning by mentioning 'optional sprint or state filter', but this does not significantly enhance understanding beyond the schema.

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 lists agile stories and mentions optional sprint or state filters. It is specific and distinguishes from sibling list tools like list_epics or list_scrum_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 when to use filters but does not explicitly state when to use this tool versus alternatives or provide exclusion criteria. Usage guidance is implied but not comprehensive.

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