Restore Custom Taxonomy

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

Discloses that the restored taxonomy includes its full tree and becomes active (is_active=true). Annotations already declare idempotent and non-destructive; description adds return context without contradiction.

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?

Single sentence that is front-loaded with action and result, no redundant words.

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?

Covers the essential action and return value. Lacks mention of error cases (e.g., taxonomy not found or already active), but sufficient for a simple one-parameter operation.

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% with a clear description of taxonomy_id requiring is_active=false. Description adds no extra semantic information beyond what the schema already provides.

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?

Clearly states 're-activate' a soft-deleted custom taxonomy, distinguishing it from sibling tools like delete_custom_taxonomy and update_custom_taxonomy.

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?

Implies use when a taxonomy is soft-deleted (is_active=false), but does not explicitly state when not to use or mention alternatives like update_custom_taxonomy.

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