assess_server

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

With no annotations provided, the description discloses behavioral traits: advisory nature, conformance monitoring not enforced, and potential UNVERIFIED verdicts. This adds valuable context beyond a simple read operation, though no side effects or auth needs are mentioned.

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?

Three concise sentences without redundancy: purpose, use, and behavioral notes. Front-loaded with the core action, efficient and clear.

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 covers purpose, usage guidance, verdict shape, and advisory nature. For a simple one-parameter tool with no output schema, it provides sufficient context, though explicit mention of return format would be slightly better.

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 single parameter 'server_id' is described in the schema as 'Server slug to assess.' The description does not add new meaning beyond usage context. With 100% schema coverage, a baseline of 3 is appropriate.

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 performs an aggregated pre-flight trust assessment across all tools on a server, using the specific verb 'assess' and resource 'server'. It distinguishes from sibling 'check_tool_trust' by noting aggregation, and clarifies the verdict shape is identical.

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 states the use case: 'is THIS server worth integrating?' decisions. It also provides context on when to be cautious with 'v1 advisory; conformance monitored not enforced; verdicts may be UNVERIFIED if not yet probed', guiding appropriate reliance.

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