Get Server Info

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

No annotations exist, so the description carries the disclosure burden, and it does not explicitly state that this is a non-mutating read-only introspection call or whether any auth/scope is required. It does disclose the content of the response (configuration, capabilities, tools), and the presence of an output schema removes the need to describe return structure, keeping the gap moderate rather than severe.

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?

A single front-loaded sentence with the verb first and the three returned artifacts listed compactly. There is no filler and nothing that could be trimmed without losing information.

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 zero-parameter read tool with an output schema covering the return payload, the description is nearly sufficient: it names what is returned and requires no argument knowledge. The only missing piece is the read-only/self-inspection framing, which would help an agent trust it as a safe discovery call.

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 takes zero parameters, so the baseline is 4; there are no arguments whose meaning could be ambiguous or under-documented. Nothing in the description is needed to supplement parameter semantics.

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?

Specific verb + resource: 'Get MCP server configuration, capabilities, and available tools' tells the agent exactly what is retrieved and enumerates the three content areas. It is clearly distinguished from the image-processing siblings, though it does not explicitly separate itself from discovery siblings like list_available_models or list_templates, which overlap in intent.

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?

Usage is only implied: an agent can infer this is the introspection call to make before using the other tools, but the description never states when to prefer it over list_available_models or list_templates, nor any preconditions. No explicit when/when-not guidance is present.

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