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

Annotations already declare destructiveHint=true, so the description does not need to re-state danger. It adds real value beyond annotations by disclosing that tool assignments are removed and that the reset can be previewed with apply=false; it could say more about whether the reset is reversible or what happens to published versions.

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?

Three short sentences, front-loaded with the core action, followed by the immediate-effect caveat and then the side effect. No filler or repetition of the schema.

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?

An output schema exists, so return-value explanation is not needed, and the destructive nature is covered by annotations. However, for a destructive reset with four required and completely undocumented parameters, the description leaves important operational details unresolved (notably revision and number_id/direction scoping).

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 the description must carry parameter meaning, but it only explains apply. The required number_id, direction, and revision parameters have no explanation anywhere – revision (likely optimistic concurrency) and the number/direction scoping are entirely left to inference from bare type/enum constraints.

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: replace agent settings with defaults, and adds the notable side effect of removing tool assignments. An agent can distinguish it from update_agent conceptually (reset vs. modify), though the description never names that sibling or any other alternative.

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?

There is no guidance on when to use reset_agent rather than update_agent, discard_agent_draft, or get_agent, nor any stated preconditions. The only conditional sentence (apply=false) describes runtime behavior, not tool selection.

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