get_stories

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves 'current active stories' and notes expiration timing, but lacks critical details such as authentication requirements, rate limits, pagination behavior, error conditions, or what happens if account_id is omitted. For a read operation with zero annotation coverage, this leaves significant gaps.

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 appropriately concise with two sentences that each add value: the first states the core purpose, and the second provides important contextual information about story expiration. There's no wasted text, though it could be slightly more structured for 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?

For a simple read tool with one optional parameter and no output schema, the description is minimally adequate. It covers what the tool does and adds useful context about story lifespan, but lacks completeness regarding behavioral aspects like authentication, response format, or error handling that would be helpful for an agent.

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 100%, so the input schema fully documents the single optional parameter. The description doesn't add any parameter-specific information beyond what's in the schema, such as clarifying when account_id is needed or how it's obtained. Baseline 3 is appropriate when the schema handles parameter documentation.

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's purpose: 'Get current active stories on your Instagram account.' It specifies the verb ('Get'), resource ('stories'), and scope ('current active'), but doesn't explicitly differentiate from sibling tools like 'get_media_posts' or 'get_mentions' that might also retrieve Instagram content.

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 no guidance on when to use this tool versus alternatives. It mentions that 'Stories expire after 24 hours,' which is contextual information but doesn't help the agent choose between this tool and other content-retrieval siblings like 'get_media_posts' or 'get_hashtag_media.'

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