Server Statistics

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

With no annotations provided, the description must carry the full burden of behavioral transparency. It states what the tool returns but does not disclose whether the operation is read-only, whether it requires specific permissions, or any potential side effects. The name suggests a read operation, but the description does not explicitly confirm safety or limitations.

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, well-structured sentence that front-loads the main purpose ('Returns server health metrics') and then lists specific metrics. Every word contributes meaning, with no repetition or filler.

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 the simplicity of the tool (one optional parameter) and the presence of an output schema, the description is reasonably complete. It explains what the tool returns, and the schema covers the parameter. However, it lacks usage guidance and explicit safety information, which would improve completeness.

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 input schema fully documents the only parameter (includeMemory) with a description and default value, so baseline is 3. The tool description adds no additional information about the parameter or its effect, but since schema coverage is 100%, no compensation is needed.

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 tool returns server health metrics including uptime, request count, memory usage, and OAuth provider configuration summary. It uses a specific verb ('Returns') and names the resource ('server health metrics'), but does not explicitly distinguish it from sibling tools like query_analytics or list_server_capabilities.

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 server health metrics are needed, but provides no explicit guidance on when to prefer this tool over alternatives or when not to use it. There is no mention of exclusions or prerequisites, so the guidance is only implicit through the stated purpose.

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