stories-create

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

No annotations provided, so description must carry full transparency burden. Only states creation and a parameter constraint, lacking details on side effects, permissions, rate limits, or what happens post-creation (e.g., return value). Minimal behavioral disclosure.

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?

Extremely concise: one sentence for purpose and one brief constraint. No filler, front-loaded with action, earning its space.

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 creation tool with 8 parameters, no output schema, and no annotations, the description is insufficient. It lacks details on return value, prerequisites (authentication, permissions), or behavioral context to help the agent use it correctly among many sibling tools.

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% (all parameters described). The description adds crucial conditional constraint ('either team or workflow') not captured in the schema's required array. This adds significant value beyond the schema, justifying a 4.

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?

Description clearly states 'Create a new Shortcut story' with a specific verb and resource. The additional requirement clarifies the core parameters, distinguishing from other story-related tools like stories-update or stories-search.

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?

Provides a key guideline (requires name and either team or workflow) but does not explicitly state when to use this tool over siblings like stories-create-comment or stories-search. Implicitly it's for creation, but no 'when not to use' or alternative hints.

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