list-tags

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

The description implies a read-only operation, which is consistent with a list tool. However, it does not disclose any additional behavioral traits such as permissions, rate limits, or default behavior beyond what is in the schema.

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 a single sentence with no wasted words. However, it is so brief that it sacrifices clarity on the 'classification filtering' aspect.

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 tool with 6 parameters described in the schema, the description omits explanations for fields, include, and the cursor-based pagination mechanism. The mention of 'classification filtering' is vague and incomplete.

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 description mentions 'classification filtering' but the schema has no such parameter; it has a 'parent' filter and 'include' for deleted entities. This mismatch could mislead the agent. With 100% schema coverage, the description adds little value and introduces ambiguity.

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 lists tags with pagination and classification filtering, which distinguishes it from sibling list-* tools for other entities. However, it does not specify scope like 'list ALL tags'.

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?

No guidance is provided on when to use list-tags versus other list-* tools (e.g., list-classifications, list-tables). The description only states what the tool does.

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