splunk_get_server_info

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

No annotations, so the description carries the disclosure burden. 'Retrieve' implies a read-only operation, but it doesn't state permission requirements, whether license/topology data can be slow or costly to gather, or anything about the response shape (which the output schema covers).

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?

One front-loaded sentence that names the action first and then the returned fields. Zero waste, no 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?

For a parameterless read tool with an output schema, the description covers what is needed to select and call it. The remaining gap is routing guidance against the sibling health/license/topology tools.

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 takes zero parameters, so the baseline is 4. There is nothing about arguments for the description to clarify, and it correctly stays silent on inputs.

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?

A specific verb (Retrieve) plus resource (Splunk server runtime info) with an enumerated payload: version, OS, license state, topology roles. That distinguishes it reasonably well from splunk_get_server_health and splunk_get_license_usage, though no sibling is named explicitly.

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?

There is no guidance on when to use this versus splunk_get_server_health, splunk_get_license_usage, or splunk_get_cluster_health, which overlap on license and topology content. Usage is at best inferable from the returned fields; no conditions or exclusions are stated.

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