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

Goes well beyond the annotations: describes the HUMAN_EDIT_AFTER_AGENT_SYNC conflict, that the override is audit-logged, and that an unrecognised status returns an error enumerating valid columns. Annotations (idempotent, non-destructive) are consistent with a status transition that is safe to retry, and the description adds the concurrency-safety context they omit.

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?

Front-loads the action in the first clause and every following sentence carries operational content (accepted values, identification, error behaviour, conflict path). Slightly dense with em-dashes and parentheticals, but no filler to cut.

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 mutation tool with a conflict/override path, no output schema and four fully documented params, the description covers what changes, how to identify the target, what errors mean, and how to recover. Nothing an agent needs in order to call it safely is missing.

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 100%, so the baseline is 3; the description still adds value by explaining that `status` accepts either a universal category or an exact custom column name, with concrete examples ('Code Review', 'QA'), and by giving the ticket-key example format for `storyId`. The gating rule around `force` (explicit human approval, audit-logged) is restated beyond the schema but adds the consequence of misuse.

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?

States a specific verb and resource ('Transition a story's status') plus the optional comment side-effect, so the agent knows exactly what changes. It references siblings stride.list_workflow_stages and stride.get_story but never explicitly says how it differs from stride.update_story or stride.bulk_update_stories, which is the one ambiguity an agent would still have.

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?

Explicit when-to-use and when-not: use a category or a column name from stride.list_workflow_stages, call stride.get_story first on a conflict, and only pass force:true with explicit human approval. It also tells the agent what happens on failure (error listing the project's columns), which functions as a recovery path.

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