server_info

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

With no annotations provided, the description carries the burden. It states 'non-secret' and uses 'Return' which implies a read-only, safe operation. This adds value beyond the tool name and schema, though it doesn't detail performance or side effects. Given the zero-parameter nature, this transparency is adequate.

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 fully defines the tool's purpose. It avoids fluff and includes the important caveat about secrets. Every word earns its place.

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 presence of an output schema and the simple zero-parameter nature of the tool, the description provides sufficient context. It names the core output ('server info and configuration snapshot') and the non-secret guarantee. No additional detail is necessary for an AI agent to use this tool correctly.

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 has zero parameters, so per guidelines the baseline is 4. The description correctly implies the output focuses on server info/configuration, providing meaningful context even without parameters. No additional parameter explanation 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 uses a specific verb ('Return') and clearly identifies the resource ('server info and configuration snapshot'). It explicitly notes the non-secret nature, distinguishing it from potential sensitive operations. Among sibling tools that are all PDF-related, this stands out as the unique server info tool.

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 you need server info or configuration snapshot, use this tool. Since all sibling tools are PDF-specific, there is no ambiguity or competing alternative, providing clear context without explicit exclusions.

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