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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds valuable behavioral nuance beyond that: versions are immutable, hasMore indicates more items exist, and nextPageToken should only be used when every item is needed. No contradiction with annotations.

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 concise sentences, each earning its place: the core purpose, the relevant alternative, and the pagination behavior. No fluff or repetition of schema content.

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?

The schema is fully documented and there is an output schema, so the description need not re-explain return values. The description covers immutability, the get_classifier alternative, and pagination. The only slight gap is the vague 'narrowing filters' advice, but overall the definition is complete enough for correct tool selection and invocation.

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?

Since the schema already describes 100% of parameters, the baseline is 3. The description adds extra practical guidance about nextPageToken and hasMore, telling the agent not to paginate unless necessary and to prefer filters. This is useful but the phrase 'narrowing filters' is a bit vague given there are no explicit filter parameters beyond the required identifiers.

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 states a specific verb and resource: list a classifier's published, immutable versions汪汪. It also names the classify group and points to get_classifier for fetching one version's config, distinguishing it from related list tools and the singular get tool. This is tightly scoped and unambiguous.

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 clear context and an explicit alternative for fetching a single version's config. It also provides pagination guidance about hasMore and nextPageToken. It does not explicitly contrast with list_classifiers or state when not to use this tool, but the purpose is clear enough that the usage context is well implied.

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