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

Even though annotations already declare readOnlyHint, idempotentHint, and destructiveHint, the description adds substantial context: it returns only lookup data, absence means 'not measured' not zero, covers only crypto/Web3, updates weekly, and has no authentication or rate limits. This goes well beyond what annotations provide.

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 bit long but every sentence contributes value: purpose, usage, contrast with sibling, caveats, data licensing. It is front-loaded with the core purpose and then expands into use cases and policies. Slightly more compact would be ideal, but it is well-organized and not redundant.

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?

With no parameters and an output schema present, the description covers all necessary operational context: what data is returned, how to use it, what it doesn't do, its coverage scope, update frequency, and data usage terms. It is fully complete for an agent to select and 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 tool has zero parameters, so the baseline is 4. The description clarifies that the output consists of names and slugs only, which adds meaning beyond the title. Since there are no parameters, no further parameter-level detail is needed.

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 names and slugs of every brand in the DABLOCK index, explicitly framing it as a lookup table. It distinguishes itself from sibling tools by naming get_brand_visibility and get_visibility_index and explaining how it differs.

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 provides explicit use cases: converting a brand name to a slug for get_brand_visibility, and checking if a brand is tracked. It also gives a clear 'Do NOT use' condition with a recommended alternative (get_visibility_index), making when-to-use and when-not-to-use unambiguous.

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