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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known, yet the description adds substantial context: archived tasks are never deleted and remain searchable and visible in sprint history, there is no count/selection and no undo on this surface, and a second call is a no-op. It also prescribes confirming with the user first.

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-loaded with the trigger condition, then consequences, then the confirmation requirement. Every sentence carries distinct information (scope, recoverability, alternatives, idempotence) with no filler.

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 zero-parameter, no-output-schema mutation, the description covers everything an agent needs: when to invoke, what is affected, what is reversible, alternatives, and the confirmation requirement. Nothing material is left unspecified.

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?

Zero parameters, so the baseline is 4. The description does add one useful semantic point the empty schema cannot convey — it operates on the WHOLE column in a single call with no count — which clarifies why no parameters exist, but it goes no further than that.

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 (archive) and resource (every task in the Done column), and explicitly distinguishes itself from complete_sprint (which archives a sprint's tasks automatically) and restore_task (which works on the trash, not the archive). An agent can select it correctly without opening any schema.

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?

Gives concrete user phrasings that trigger it ('archive everything in Done', 'clean up the board'), names the alternative (complete_sprint already covers sprint-scoped archiving; restore_task covers trash), and states an explicit exclusion: never call it to tidy up on your own initiative.

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