List Story Branches

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

With no annotations, the description must state behavioral traits. It only says 'List,' suggesting a read operation, but does not confirm safety, return format, or any side effects. This is minimal and leaves the agent guessing.

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?

One sentence, zero fluff, front-loaded with the action. It is appropriately concise.

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 lacks an output schema and annotations. The description does not mention the return shape, pagination, or dry_run semantics, making it incomplete for an agent to fully understand the tool's behavior.

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 coverage is 0%. The description adds context for story_id via 'Shortcut story' but does not explain the dry_run parameter at all. The schema only provides names/types.

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 uses a specific verb 'List' and names the resource 'Git branches' with a clear context 'associated with a Shortcut story.' It is distinct from sibling tools like list_story_commits and list_story_pull_requests.

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 when you need branches for a story but provides no explicit alternatives or exclusions. Sibling tools like list_story_commits exist but no comparison is made.

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