update_story

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

No annotations provided, so description carries full burden. It only mentions 'update', a common mutation verb, but does not disclose idempotency, error handling for missing slug, partial update semantics, or response format. Limited transparency beyond basic operation.

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?

Single sentence with no redundancy or unnecessary detail. Action and target are stated first, efficiently conveying the core purpose.

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 high complexity (14 parameters, nested objects, no annotations or output schema), the description is severely underspecified. It omits details on optional fields, update behavior, and return values, leaving the agent with insufficient context for accurate invocation.

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 0%, so description must compensate. Only the slug parameter is hinted ('by slug'). The other 13 parameters, including nested objects with enums, receive no explanation. The description adds minimal value over the schema's raw structure.

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 'Update an existing story by slug', identifying the action (update) and resource (story) with a specific identifier (slug). This distinguishes it from create_story, delete_story, and get_story without ambiguity.

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 modifying existing stories, but provides no explicit guidance on when not to use it (e.g., if story does not exist) or alternatives (e.g., create_story for new stories). Minimal but not misleading.

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