GetStories

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description contributes only the scoping detail that it reads from the currently loaded project, and says nothing about the shape or granularity of the story data returned.

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 core sentence is short and front-loaded, but the trailing '(Tapir, Project Commands)' tag is unexplained metadata noise and 'sructure' is a typo that slightly undermines 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?

With no parameters, no output schema, and read-only annotations, the definition is nearly sufficient for invocation. However, because there is no output schema, the description should say what story information is returned (names, elevations, levels) rather than just 'information about the story structure'.

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 tool takes zero parameters, so the baseline is 4. The description correctly implies the tool is parameterless by scoping everything to the currently loaded project.

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 pairs a clear verb ('Retrieves') with a specific resource ('the story structure of the currently loaded project'), so an agent knows this returns floor/story data. It does not, however, differentiate itself from siblings such as GetProjectInfo or GetAllElements, which also describe project-level retrieval.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The phrase 'currently loaded project' hints at the required context, but nothing tells the agent when this tool is preferable to GetProjectInfo or the element-listing siblings.

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