get_v1_user_stories_by_username

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions relative speed, which is minimal. Does not cover auth, rate limits, or other important behaviors.

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 concise (two sentences) but awkwardly structured: the speed note precedes the main action. Every sentence has a purpose, but clarity could be improved.

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 multiple sibling tools and 3 parameters, the description is insufficient. It doesn't explain what 'user stories' entails, how 'amount' affects results, or how this differs from similar endpoints.

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 only 33% (only 'force' has a description). The description adds no parameter-level details beyond the schema, failing to explain 'amount' or 'username'.

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 'Get user stories' with a specific resource. The endpoint path is included. However, it does not explicitly differentiate from sibling tools like get_v1_user_stories or get_v2_user_stories_by_username, leaving some ambiguity.

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 a speed comparison, suggesting an alternative endpoint for faster responses. This gives some guidance on when not to use this tool, but lacks explicit when-to-use criteria or full enumeration of alternatives.

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