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

Since no annotations are provided, the description carries the behavioral transparency burden. It usefully discloses that results are distinct capability tags, include usage counts, and are sorted by usage order. However, it does not describe output format, pagination behavior, or edge cases such as empty directories.

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, tightly worded sentence with no filler. Every phrase adds information: distinctness, resource type, scope, aggregation, and sort order.

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 simple tool with one optional parameter and no output schema, the description gives the core return concept but omits important invocation context: how the limit parameter behaves, what the response structure looks like, and whether the data may be stale or filtered. The absence of parameter documentation makes it incomplete for reliable agent 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?

Schema description coverage is 0%, and the only parameter 'limit' has no schema description. The tool description does not mention the limit parameter at all, so the description fails to compensate for the missing parameter semantics. An agent cannot confidently know how limit affects the results.

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 identifies the resource (capability tags in the directory) and the key behavior (returning distinct tags with usage counts, sorted most-used first). It is distinguishable from siblings like list-domains or search-agents, though it lacks an explicit verb and does not name any sibling for contrast.

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 states what the tool returns and the sort order, but it gives no guidance on when to choose this tool over alternatives such as search-agents or list-domains. There are no usage conditions, exclusions, or sibling comparisons.

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