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

Annotations already indicate the tool is destructive. The description adds the two-minute lock detail, which is a meaningful behavioral constraint. However, it does not explain the consequences of the lock or what 'cancel' entails beyond the annotation, so transparency is moderate.

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, succinct sentence that immediately conveys the core action and timing. There is no redundant language, and it is front-loaded with the verb.

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 description lacks essential details about the required parameters and the meaning of the two-minute lock. While annotations cover the destructive nature, the description does not explain prerequisites, effects, or error conditions, making it insufficient for reliable tool selection and 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?

The description does not mention the parameters at all, and the schema has no descriptions for lineKey or draftRevision. With 0% schema coverage, the description fails to clarify what these parameters represent or how to populate them, leaving the agent without guidance.

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 action (cancel) and resource (one line schedule), and the 'two-minute lock' condition distinguishes it from publish/draft tools. It could be clearer about what 'line schedule' refers to, but it is sufficiently specific.

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 canceling a scheduled publish before a two-minute lock, but it does not explicitly compare to sibling tools like schedule_line_publish or discard_line_draft. No exclusions or after-lock guidance are provided, leaving usage context partially implied.

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