list_system_status

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is established. However, the description adds no behavioral information beyond the HTTP method, such as authentication needs, response behavior, or any side effects. It relies entirely on the structured annotations.

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 extremely compact and front-loaded with the action. The endpoint line is useful, though the prose 'Read System.' is somewhat redundant with the tool name and endpoint. Still, there is no unnecessary verbosity.

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 simple, read-only, parameterless status endpoint with a rich output schema and clear annotations, the description provides enough to invoke the tool correctly. It does not explain what the status payload contains, but the output schema covers that, and no other operational context seems essential for this low-complexity operation.

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 and schema description coverage is 100%, so there is no parameter documentation burden for the description to carry. The baseline for a parameterless tool is appropriately met.

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 identifies a clear read operation via the HTTP endpoint GET /api/v3/system/status, so an agent understands the resource being queried. 'Read System' is terse, but the endpoint removes ambiguity and distinguishes it from the many other list_* and system-related sibling tools.

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 tool versus alternatives such as list_system_task, list_system_backup, or list_system_routes. No context, exclusions, or alternative tool references are provided, so an agent must infer usage from the name and endpoint alone.

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