check_conformance

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

No annotations are provided, so the description carries the full burden. It states the tool runs 18 checks and returns a grade, but does not disclose whether it is read-only, requires authentication, has destructive potential, or any error conditions. The conformance condition is mentioned, but overall behavioral traits are incomplete.

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 concise sentences that immediately convey purpose and key details (checks, tiers, grade). Every sentence adds value with no redundancy.

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 the tool's complexity (18 checks, 3 tiers, grading) and the presence of an output schema (not shown), the description covers all essential aspects for an agent to understand what the tool does and what it returns.

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 covers the single parameter (url_or_path) with a clear description. The tool description adds no further meaning beyond what the schema already provides. With 100% schema coverage, 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 uses a specific verb ('score') and resource ('MCP server manifest'), clearly distinguishing from sibling tools that scan content or credentials. It explicitly mentions the number of checks (18), tiers (REQUIRED, RECOMMENDED, BEST PRACTICE), and grading scale (A+ to F).

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 the tool is for testing conformance but lacks explicit guidance on when to use it versus alternatives, when not to use it, or prerequisites. Sibling tools are different in purpose, but no comparative advice is given.

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