list_ig_stories

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

With no annotations, the description carries the full burden; it does disclose the key temporal behavior (only active, 24-hour stories). However, it does not state the read-only nature, token/permission requirements, or pagination behavior.

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?

A single front-loaded sentence with no filler every word adds meaning. It is efficient, though the terseness leaves param and usage details uncovered.

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 is simple (one required param) and an output schema exists, so return-value details are covered elsewhere. The main gaps are parameter provenance and permission preconditions, which an annotation-less description should address for fully confident invocation.

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 0% and the description never mentions ig_user_id. The parameter name is self-descriptive, but nothing explains where the ID comes from (e.g., via find_instagram_account) or what format is expected.

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 a specific verb (list), a clear resource (Instagram stories), and a scope qualifier (active within 24h), so an agent can tell what is returned. It is distinguishable from siblings like list_ig_media or get_ig_story_insights, though it does not explicitly name any alternative.

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 such as list_ig_media or get_ig_story_insights, and no prerequisites or exclusions are mentioned. The agent must infer selection logic purely from names and context.

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