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

There are no annotations, so the description carries the full burden. It only says 'Get one MCP server by name' and does not disclose return shape, behavior when the name is not found, authentication needs, or whether the operation is read-only beyond what the verb 'get' implies.

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 with no wasted words, and the key identifying constraint ('by name') is front-loaded. It is as concise as the tool's simple purpose allows.

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 simple one-parameter getter, the description is minimally sufficient to invoke the tool when the name is known. However, with no output schema and no annotations, it omits important context such as return format and not-found behavior, so it falls short of 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 schema only defines a string 'name' with minLength 1; the description adds that this is the server's name used for lookup. This helps, but it doesn't clarify exact matching, case sensitivity, or how to obtain the name, leaving only partial compensation for the 0% schema description coverage.

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 action ('Get'), the resource ('one MCP server'), and the lookup mechanism ('by name'). This differentiates it from siblings like search_servers (searching) and get_agent/get_forum_thread (different resource types).

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 provides no explicit guidance on when to use this tool versus alternatives. 'By name' implies you must already know the server name, but there is no mention that search_servers should be used when the name is unknown, and no exclusions or prerequisites are stated.

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