Inspect published contract

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses that the tool returns manifests, deny-list ids, and a statement of what the server is not, indicating a read-only inspection. However, it doesn't mention any potential side effects, resource costs, or error behavior. For a simple read-only tool this is adequate but not rich.

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 a single sentence that directly states what is returned. No filler, every word earns its place, and the key outputs are front-loaded. This is appropriately concise for the tool's simplicity.

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 parameterless inspection tool with no output schema, the description covers the essential return values. It doesn't explain what 'tool manifest' or 'resource manifest' mean, but that may be domain-specific. It also doesn't clarify when to choose this over siblings, but given the tool's narrow scope, it's relatively complete.

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 tool has zero parameters, so there is nothing for the description to explain. The baseline for 0 parameters is 4, and the description doesn't need to compensate for any schema gaps. The tool is straightforward in that regard.

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 clear verb ('Return') and specifies the resource (contract information: tool manifest, resource manifest, deny-list ids). It is specific about what is returned, but it doesn't explicitly contrast with sibling tools like list_catalog or explain_deny, leaving some ambiguity about what makes this unique.

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 it (for inspecting the server's contract) but doesn't state explicit conditions or exclusions relative to the siblings. It doesn't say 'use this when you need an overview' or 'don't use this for looking up specific operations'. Context is somewhat clear but not fully articulated.

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