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

With no annotations, the description carries the full burden. It clearly discloses the tool's main behavior: returns a verdict, a reason, and the full rating, and defines each verdict value. However, it does not mention potential edge cases like network failures, timeout behavior, or whether the tool has any side effects, though the mutating nature is clearly absent from the description.

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 front-loaded with the core command ('THE GATE — call this before...'), then delivers verdict semantics and alternatives in a compact, scannable format. Every sentence adds necessary information, and the example is valuable for parameter format.

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 description explains the return value (one-word verdict, reason, full rating) and the meaning of each verdict, which is essential given the absence of an output schema. It also covers sibling alternatives. It could be more complete by mentioning the batch 'names' parameter and error handling, but overall it is sufficiently complete for a simple vetting tool.

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 100%, so the baseline is 3. The description adds a concrete example and stresses 'exact' registry name, which reinforces the 'name' parameter. However, the narrative only mentions 'name' and omits the 'names' array parameter, although the schema already documents it fully, so no significant gap exists.

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's action: 'call this before your agent depends on a tool you don't already trust' and specifies the resource (exact server registry name) and output (one-word verdict allow/warn/block with reason and full rating). It also distinguishes itself from siblings by explicitly directing users with a 'NEED' to find_tools and those with a 'fuzzy name' to resolve_server_name.

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?

Usage context is explicit: use before depending on an untrusted tool. It also provides concrete alternatives for different situations ('If you have a NEED not a name, use find_tools; if you have a fuzzy name, use resolve_server_name'), and explains the meaning of each verdict ('block' = don't depend, 'warn' = look first, 'allow' = safe to depend).

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