get_v1_user_stories

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

The description only includes billing information (2 requests per call). It does not disclose behavioral traits such as mutability, side effects, or response structure. Since annotations are absent, the description fails to compensate for the lack of behavioral context.

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 extremely concise (two lines), which is efficient, but it sacrifices necessary detail. Every sentence is short, but the overall structure lacks completeness.

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 tool has 3 parameters, no output schema, and multiple siblings, the description is woefully incomplete. It fails to clarify return values, parameter usage, or how it differs from similar tools, making it insufficient for effective agent use.

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?

With only 33% schema description coverage, the description adds no explanation for the parameters. It does not mention 'user_id', 'amount', or provide context beyond what is in the schema, leaving the agent unclear about their semantics.

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 states 'User Stories' and provides the endpoint path, giving a basic idea that it fetches user stories. However, it lacks specificity about what constitutes a user story (e.g., Instagram stories) and does not differentiate from sibling tools like get_v1_user_stories_by_username.

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?

No guidance is provided on when to use this tool versus siblings. The description does not mention filtering, prerequisites, or alternatives, leaving the agent to infer usage context from the tool name alone.

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