system_info

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

No annotations exist, so the description carries the full burden for behavioral disclosure. It mentions only the endpoint and a high-level intent, without stating that it is read-only, what kind of data it returns, whether authentication is needed, or whether there are any side effects. 'Info' weakly implies a safe read, but that is not explicit.

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 sentence with no wasted words. It provides the key scope ('high-level panel info') and the endpoint, making it easy to parse quickly.

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 informational tool with an output schema, the description is largely sufficient. It could be more explicit about how it relates to the many system_* siblings, but an agent can likely invoke it correctly based on the endpoint and 'high-level panel info' alone.

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 is already complete and parameter documentation is not needed. The description's endpoint reference adds minor context, but the baseline for a no-parameter tool is appropriately high.

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 the resource ('panel info') and gives the endpoint, clearly indicating this is a general system information read. It is somewhat vague with 'high-level' and does not explicitly state how it differs from siblings like system_version or system_cpu, but it is enough to understand the basic function.

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 the many sibling system_* tools. 'High-level panel info' only implies it might be an overview rather than a specific metric, but no alternatives, exclusions, or conditions are provided.

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