list_system_settings

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description's "Get" plus GET /system/settings are consistent with that safety profile. The description adds no behavioral context beyond the annotations (no auth, rate limits, or output characteristics), but because the annotations carry that burden, this is acceptable with no contradiction.

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?

Two short lines with no wasted words; the endpoint line adds useful HTTP-path context. It is appropriately sized for a zero-parameter read tool, though "Get System Settings" adds little beyond the tool name itself.

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 correct invocation, the definition is nearly sufficient: no parameters to pass, an output schema covers return values, and annotations cover safety. The gap is that it never clarifies what 'system settings' contains or how this endpoint differs from list_server, list_system_agents, and list_system_updates, leaving tool-selection ambiguity unresolved.

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 description has nothing to explain and the baseline for a zero-param tool applies. Schema coverage is trivially 100% with an empty properties object.

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?

"Get System Settings" states a clear verb (Get) and resource (System Settings), and the included endpoint 'GET /system/settings' confirms the read operation. However, with closely named siblings like list_server, list_servers, list_system_agents, and list_system_updates, the description does nothing to differentiate what uniquely constitutes 'system settings,' leaving some selection 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?

No guidance is given on when to use this tool versus alternatives. It names no sibling, states no exclusions, and provides no conditions for use — a notable gap given the large number of list_* sibling tools.

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