Get server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It merely restates the operation without explaining whether it is read-only, what data it returns, or any side effects. The word 'Get' implies a read operation, but no explicit context is added.

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, short sentence that is front-loaded with the action and object. It is concise and every word is necessary, with no 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?

For a simple get-by-id tool, the description is minimally adequate, telling the agent to fetch server details by UUID. However, it does not clarify what 'details' includes, nor does it differentiate from listServers or mention any limitations. Without an output schema, the return structure is unspecified, but for a straightforward retrieval, the description gives enough to proceed.

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 has a single parameter (uuid) with no description (0% coverage). The description's 'by UUID' merely reiterates the parameter name, adding minimal semantic value. It does not explain the expected format or any constraints beyond what the parameter name suggests.

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 'Get server details by UUID' clearly states the tool's purpose with a specific verb (Get) and resource (server details), and specifies the identifier (UUID). It distinguishes from sibling listServers by focusing on a single server.

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 provides no guidance on when to use this tool versus alternatives such as listServers. It does not mention any exclusions, prerequisites, or alternative tools. The usage context is only implied by the name and the parameter.

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