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

Without annotations, the description carries full burden for behavioral disclosure. It indicates a read operation via 'Get' but does not elaborate on side effects, authorization needs, rate limits, or what 'full card' entails. The description is minimally transparent.

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 concise with no wasted words. It is front-loaded with the action and resource. However, it could be slightly expanded with additional context without losing conciseness.

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 an output schema exists, return values are already documented. However, the description lacks guidance on prerequisites, such as needing a valid slug, or any edge cases. For a simple fetcher, it is partially complete but could be richer.

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?

With 0% schema description coverage, the description adds the phrase 'by slug,' which clarifies the parameter's purpose. However, it does not provide format, constraints, or examples beyond the schema's basic type definition. The added value is moderate.

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 'Get the full card for one MCP server by slug,' specifying the action (get), resource (full card for one MCP server), and the parameter (slug). It effectively distinguishes itself from sibling tools like search_mcp_servers, which would return multiple results.

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 a specific slug is known but offers no explicit guidance on when to use this tool versus alternatives like search_mcp_servers or get. No exclusions or conditions are mentioned.

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