get_taxonomy_nodes

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

No annotations present; description only states it fetches the full taxonomy tree without disclosing side effects, authentication needs, rate limits, or response format. The return structure is not described, leaving the agent uncertain about how to process the output.

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?

Two short sentences, no fluff. First sentence states the action, second provides usage guidance. Efficient and easy to parse.

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?

Despite having no parameters and no output schema, the description fails to describe the response format. For a tool returning a 'full tree', the agent needs to know if it's a list of nodes, a nested structure, etc. The description omits this essential context.

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?

No parameters, so schema coverage is 100%. The description implies no input is needed, which is sufficient. Baseline for zero parameters is 4.

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?

Description clearly states 'Get the full Etsy seller taxonomy tree' and specifies the use case for finding taxonomy_id for create_listing. Differentiates from sibling 'get_taxonomy_properties' which likely deals with properties of a node, not the hierarchy.

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?

Explicitly directs to use this tool for finding taxonomy_id for create_listing, giving clear context. Does not mention when not to use or alternatives, but the use case is specific and helpful.

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