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

With no annotations, the description carries the full burden of behavioral disclosure. It states the tool returns full metadata and includes payment protocol detection, which conveys a read-only operation. However, it does not disclose potential side effects, error conditions, or whether network access is required, leaving some ambiguity.

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 three short sentences, each earning its place: it states the core function, acceptable inputs, and a notable feature. There is no redundancy or unnecessary 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?

The tool has a single parameter and no output schema, so the description must infer return value expectations. It explains the full metadata promise and highlights payment protocol detection, giving a reasonable picture of the output. It does not exhaustively list fields, but for a simple inspection tool, it is sufficient.

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 coverage is 100% with the parameter 'identifier' clearly described as a reverse-DNS name, URL, or keyword. The description repeats this exact information but adds no new semantics beyond the schema, so the 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 retrieves full metadata for any MCP server, using a specific verb ('Get') and resource ('MCP server'). It also highlights flexible input formats and a unique feature (payment protocol detection), which helps distinguish it from sibling tools like catalog, checkout, and search.

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 usage when metadata about a server is needed, and the input flexibility (reverse-DNS, URL, keyword) provides some practical guidance. However, it does not explicitly state when to use this tool over siblings or when not to use it, so it lacks strong usage differentiation.

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