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

Annotations already declare read-only, idempotent, open-world, non-destructive, and the description adds substantial context beyond them: authentication requirements, crawling limits (no redirect following, no schema-reference resolution), and no execution of discovered service tools. The closing caveat that results are observed metadata rather than a security certification sets accurate expectations about the output's trustworthiness.

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?

Four compact sentences, no filler: prerequisite first, then the action, then hard constraints, then the reliability caveat. The negative constraints are compressed into one efficient list rather than repeated prose.

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?

An output schema exists, so return values need no explanation, and annotations plus the description together cover safety, auth, and network-scope behavior well. The only real gap is guidance on the endpoint string's accepted format, which matters for a tool with a single required input.

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 `endpoint` parameter has 0% schema description coverage, so the schema supplies only type and length bounds. The description partially compensates by implying the value must be a public HTTPS URL, but it says nothing about accepted path forms, trailing slashes, or whether a scheme must be included.

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 names a specific verb and object: inspect a public HTTPS MCP endpoint's tool inventory and authentication response. That is clearly distinct from the site/llms.txt-oriented siblings, though it never explicitly contrasts itself with them. Purpose is unambiguous but sibling differentiation is left implicit.

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?

It states a concrete prerequisite (tools:run scope via free integration key or OAuth) and a list of excluded inputs (credentials, query strings, private addresses, redirects), which effectively defines when the tool will not work. It does not point to an alternative tool for those excluded cases, so the when-not guidance is incomplete rather than absent.

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