list_stories

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

No annotations are provided, so the description carries the burden. It states the tool is read-only ('read-only delivery status'), which is a key behavioral trait. However, it does not disclose details like whether it returns all stories or pagination, or any rate limits. The read-only hint is useful but minimal.

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 a single, concise sentence that conveys the purpose and key trait (read-only). No wasted words, front-loaded with the action and resource.

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's simplicity (one optional parameter, no output schema), the description is adequate but not rich. It does not mention what the output looks like (e.g., a list of IDs with statuses), but the description implies that. It could benefit from noting that it returns a list, but it's not critical.

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?

The schema has one optional parameter 'status' with an enum of 'ready' and 'waiting'. The description does not explain the parameter's meaning beyond the schema, but the schema itself is self-explanatory with the enum. Since schema coverage is 0%, the description could have added context, but the parameter is simple and the enum values are clear.

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 lists iKAOS Story IDs and their read-only delivery status, which is a specific verb+resource combination. It distinguishes from siblings like update_story_image or save_story_content, which imply mutations, while this is a read-only listing.

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 implies usage for retrieving story IDs and statuses, but does not explicitly state when to use this tool versus alternatives like get_story_context or get_story_rules. It lacks explicit exclusions or alternative guidance, but the read-only nature is clear.

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