edit_story

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

Annotations already indicate a write operation (readOnlyHint=false), non-destructive (destructiveHint=false), and idempotent (idempotentHint=true). The description adds no behavioral context beyond the verb 'edit'—no mention of side effects, field replacement semantics, permissions, or response behavior.

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 a single sentence, which is concise and front-loaded. However, the inclusion of '(v9.0)' is unnecessary clutter that adds no functional value, slightly reducing structural efficiency.

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 tool with 7 parameters, no output schema, and minimal annotations, a one-sentence description is drastically insufficient. It fails to explain story editing semantics, constraints, or expected outcomes, making it nearly impossible for an agent to invoke the tool correctly.

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?

With schema description coverage at 0%, the description was required to compensate for the lack of parameter documentation, but it mentions none of the 7 parameters (e.g., caption, areas, parse_mode). The agent receives no explanation of what these fields mean or how to use them.

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 verb 'Edit' and the resource 'posted story', making the tool's function immediately obvious. This also distinguishes it from sibling tools like 'post_story' or 'delete_story', which handle creation and removal respectively.

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 offers no guidance on when to use this tool versus alternatives such as 'post_story' or the 'edit_message_*' family. It lacks any mention of prerequisites, exclusions, or contextual cues, leaving the agent to infer usage solely from the tool name.

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