get_server_settings

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

The annotation already indicates readOnlyHint=true, and the description adds the important behavioral requirement 'Requires ADMIN', which is not conveyed by the annotation. This is valuable context for the agent. However, it does not elaborate on other behavioral aspects, but for a simple getter this is sufficient.

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 concise sentence: 'Get server settings. Requires ADMIN.' It conveys purpose and an important prerequisite with no wasted words, making it easy to process.

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 zero-parameter, read-only getter with an output schema, the description is complete. It states the purpose and the admin requirement, and the output schema covers the return value. No additional context is needed given the tool's simplicity.

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 the input schema fully covers parameters. The description adds no parameter details, but that is unnecessary. With zero parameters, the baseline score of 4 is appropriate.

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 action ('Get') and the resource ('server settings'), making it easy to understand what the tool does. It is concise and specific, though it does not explicitly distinguish it from the sibling tool 'get_server_info', which could cause slight ambiguity.

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 only usage guidance provided is 'Requires ADMIN', which is a prerequisite rather than an explanation of when to use this tool versus alternatives. It does not mention any exclusions or alternative tools such as 'get_server_info' or 'update_server_settings'.

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