supervisor_get_core_info

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

No annotations provided, but the description is clear that it's a read operation ('Get info'). No behavioral quirks expected; simple retrieval. Could mention it is read-only or safe, but not necessary given the simplicity.

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?

Single sentence, front-loaded with the verb and resource. Every word is informative. No wasted text.

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 is sufficiently complete. It states the type of info returned. Could note that the output schema defines structure, but not necessary.

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?

There are no parameters, so the description adds value by listing the information returned (version, arch, machine), which goes beyond the input schema.

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 verb 'Get' and the resource 'info about Home Assistant Core', specifying the exact fields (version, arch, machine). It distinguishes itself from other supervisor tools like 'supervisor_get_host_info' and 'supervisor_get_supervisor_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 this tool versus alternatives like 'supervisor_get_host_info' or 'supervisor_get_supervisor_info'. Usage is implied but not clarified.

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