supervisor_get_supervisor_info

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

The description accurately indicates a read-only retrieval operation with no side effects. However, it does not disclose potential prerequisites, error conditions, or authentication requirements beyond what is obvious.

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?

A single sentence that conveys the essential purpose and available fields with no unnecessary words. Highly efficient.

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 retrieval tool with an output schema, the description lists the key fields (version, channel, healthy). It does not detail the output format, but the schema presumably covers that. The description is sufficiently complete for decision-making.

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?

No parameters exist in the input schema, so the description does not need to add parameter meaning. Baseline for 0 parameters is 4.

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 tool retrieves information about the Supervisor, specifying the fields: version, channel, healthy. It effectively distinguishes from sibling tools like supervisor_get_core_info or supervisor_get_host_info.

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 explicit guidance on when to use or avoid this tool versus alternatives. Usage is implied by the description, but it lacks when-not scenarios or comparisons to similar get-info tools.

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