server_slots

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

Describes two important behaviors: it returns a specific object when the server was not started with --slots, and it is local-node only. Sensitive tier also disclosed. No annotation contradictions.

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?

Two concise sentences, front-loaded with purpose and key details. No wasted words.

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 tool with one parameter, the description covers purpose, return on edge case, scope, and sensitivity. Complete without needing output schema.

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 describes port parameter fully, and description does not add additional parameter-specific details beyond what schema provides. Baseline score of 3 appropriate given 100% schema 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?

Description clearly states it provides per-slot detail for a running server, including prompt text. It distinguishes from sibling tools like server_metrics and server_status by focusing on individual slots.

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?

Mentions sensitive tier and local-node only, implying grant separately from server_metrics and limited scope. However, it does not explicitly state when to use this vs alternatives like server_metrics.

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