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

With no annotations, the description carries the disclosure burden. It does disclose the output contents and the supported category depth, while 'Get' implies a read-only operation. It does not mention error handling, authentication, or rate limits, but for a simple read tool the disclosed scope is reasonably transparent.

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 two short, front-loaded sentences that convey the action, the resource, the returned fields, and the supported input scope. There is no filler and no redundant repetition of schema details.

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 one-parameter read operation with no output schema, the description provides a clear inventory of returned fields and supported slug depths, which is enough for an agent to select and call the tool. It does not describe the exact response structure or failure behavior, but that is not essential for correct 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?

The input schema already documents category_id as a slug or URL with 100% coverage, so the baseline is 3. The description adds meaningful parameter context by specifying that top-level, second-, and third-level slugs are supported, which goes slightly beyond the schema. No further parameter explanation is needed for a single-parameter tool.

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 uses the specific verb 'Get' with a clear resource, 'a Trustpilot category', and enumerates the exact returned data: display name, business count, parent category, and subcategories with ids and counts. It also clarifies the supported slug depths, which helps distinguish it from sibling tools like trustpilot_category_companies or trustpilot_category_newest.

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 when to use the tool—when category metadata is needed—and gives a useful supported-input constraint (top-level, second- and third-level slugs). However, it does not explicitly name alternatives or state when to use trustpilot_category_companies, trustpilot_category_newest, or search_trustpilot_categories instead.

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