Is this tool safe to install?

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

Description discloses return fields (vetting status, verdict, liveness, install line) and aligns with annotations readOnlyHint=true, indicating safe read operation with no contradiction.

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?

Description is concise and front-loaded, using three sentences to convey purpose, usage, and output without extraneous detail.

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?

Given simple tool with one parameter and no output schema, description adequately covers behavior and output; slight deduction for lacking example or return format details.

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 covers parameter with description ('Tool slug or name'), providing no additional meaning beyond schema; with 100% coverage, baseline score applies.

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 it provides a 'quick trust verdict' on vetting status, using specific verbs 'check' and 'vetted', and distinguishes from sibling tool 'get_tool' which offers full audit.

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?

Explicitly says 'Call this at the moment of deciding whether to install/enable a tool', and directs to 'get_tool' for full audit, though it doesn't explicitly forbid using it for other purposes.

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