List User Stories

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

With readOnlyHint=true, the safety profile is already established. The description adds valuable behavioral details: the response shape { items, pagination }, pagination fields, default page_size, and that data is read from Taiga. This goes beyond annotations without contradicting them.

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 sentences with no fluff. Front-loaded with the core purpose, then response structure and a practical hint. Every sentence earns its place without unnecessary detail.

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 description covers key aspects like response format, pagination, and a usage hint, but lacks explanations for several query parameters (q, status, epic, milestone) and does not fully clarify the return payload beyond the basic structure. Given no output schema, more detail on parameter meanings would improve completeness.

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 only 50%, and the description does not fully compensate. It explains pagination-related parameters (page/page_size) via the response shape and default, but leaves q, epic, status, and milestone undefined. It also references 'tags/assigned_to' which are not in the schema, adding confusion rather than clarity.

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 uses a specific verb 'List' and resource 'user_storys', and clarifies optional filtering by query parameters. It clearly distinguishes from sibling tools like user_story_get by focusing on listing rather than retrieving a single item.

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?

Provides clear context that this tool lists user stories with optional filters and pagination. Explicitly recommends user_story_filters_data for discovering valid filter values cheaply, which serves as an alternative for exploration. Does not explicitly state when not to use, but the context is clear.

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