server_info

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

Description states it reports configuration but does not explicitly disclose that it is a read-only, non-destructive operation. Without annotations, the description carries full burden; it is minimally adequate but lacks explicit behavioral traits.

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?

Single sentence, no wasted words. Front-loaded with purpose and action.

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?

With zero parameters and a simple read operation, the description adequately covers purpose and usage. Output schema handles return details, so description is complete enough for this complexity.

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?

No parameters (100% schema coverage). Description adds meaning about the output (access mode, safety configuration) and its purpose (knowing permitted write operations).

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 verb 'Report' and resource 'server's current access mode and safety configuration'. It distinguishes from sibling listing tools by focusing on server permissions and safety, which is unique among siblings.

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?

Explicitly says to use before write operations to check permissions. Implicit when-to-use is clear. No explicit when-not or alternatives, but no sibling serves the same purpose.

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