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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states that results are distinct, include usage counts, and are ordered most-used first. It does not mention pagination, defaults, or output format, but for a simple list operation the core behavior is adequately specified.

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?

A single, well-structured sentence delivers the essential information with no wasted words. The most important behavior (distinctness, sorting, counts) is front-loaded.

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 list tool with one optional parameter and no output schema, the description covers the key semantic output: domains, counts, and ordering. Minor gaps include default limit behavior and exact response shape, but these are not critical for an agent to invoke the tool correctly.

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 schema has 0% description coverage and the description does not explain the 'limit' parameter's meaning or effect. While the parameter name and min/max constraints are self-explanatory, the description fails to add any value beyond the schema, which is required when schema coverage is low.

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 clear verb ('list') and resource ('domain tags'), and specifies what makes it distinct: it returns distinct tags with usage counts sorted by frequency. This differentiates it from siblings like list-capabilities and search-agents, which target different data.

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 implies the appropriate use case: when the agent needs an overview of domain tags and their relative prevalence in the directory. It does not explicitly mention when not to use it or name alternatives, but the specificity of 'domain tags' provides enough context for routing.

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