Structured Entity Operations

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

The annotations declare readOnlyHint=true, indicating the tool is read-only, but the description explicitly supports write actions (create, update, delete). This is a direct contradiction. Additionally, idempotentHint=true conflicts with the non-idempotent nature of delete. The description fails to disclose behavioral traits beyond the annotations, and the contradiction severely impairs the agent's ability to use the tool correctly.

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 extremely concise, using a single sentence with embedded lists for kinds and actions. Every word serves a purpose, and the structure is front-loaded with the core purpose ('Unified CRUD across taxonomy expansion entities'). No unnecessary information is present.

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?

Given the complexity of 7 parameters, multiple kinds and actions, and no output schema, the description provides basic purpose and parameter default behavior but lacks details on return values, error handling, pagination (for list), or idempotency guarantees. The annotation contradiction further undermines completeness, making it only minimally adequate.

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 input schema has 100% description coverage, so the baseline is 3. The description adds value by stating that workspace_id and project_id default to the active scope when omitted, and that the body is free-form JSON forwarded to the API. This provides useful behavioral context not present in the schema alone.

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 tool performs CRUD operations on taxonomy expansion entities, listing all supported kinds (ticket, handoff, etc.) and actions (list, get, create, update, delete). This provides a specific verb-resource mapping. However, the term 'taxonomy expansion entities' is somewhat vague and does not distinguish this tool from sibling tools like 'batch_operations' or 'capsule'.

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 gives no explicit guidance on when to use this tool versus alternatives. It does not mention when not to use it, any prerequisites, or suggest sibling tools for different scenarios. The purpose is implied only through the listed actions and entities, leaving the agent to infer appropriate usage.

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