sac_list_stories

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

With no annotations, the description carries full burden for behavioral disclosure. It only states the tool lists stories and optionally includes models, but fails to mention important behaviors like pagination, rate limits, or that it is a read-only operation. The description is insufficient for an agent to understand side effects or constraints.

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 with two sentences containing no filler. Every word is necessary: it states the action (list), the resource (all stories), the scope (tenant), and the optional enhancement (model info). This is exemplary conciseness.

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 list tool with one boolean parameter and no output schema, the description covers the basic function. However, it lacks details on return format, pagination, or potential errors. Given the number of sibling tools, more context would help the agent distinguish when this tool is appropriate.

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 description coverage is 100% (the boolean parameter 'includeModels' is described in the schema). The tool description does not add any additional meaning beyond the schema's property description. By the baseline rule, a score of 3 is appropriate.

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 all stories in the SAP Analytics Cloud tenant and optionally includes model information. It uses a specific verb (list) and resource (stories), distinguishing it from sibling tools like sac_get_story which retrieves a single story. However, it does not explicitly differentiate from similar list tools like sac_list_models.

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 the tool is for listing all stories, but provides no guidance on when not to use it or alternatives. For instance, it does not mention that sac_get_story_detail might be better for detailed single-story retrieval. Usage context is clear but no exclusions are given.

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