system_overview

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

The description details the return values and structure, but with no annotations, it does not explicitly state that this is a read-only, non-destructive operation. It implies a safe overview query but could be more 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 well-structured: a clear one-line summary, followed by a bullet list of return keys, examples, and best practices. It is concise yet informative, with no wasted words.

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?

Given the tool has no parameters and a simple return structure, the description is complete. It includes all necessary information for an agent to understand input, output, and usage context, especially with the best practices linking to a sibling tool.

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 (schema is empty), so the description appropriately has no parameter details. With 0 parameters, baseline 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's purpose: 'Get a comprehensive overview of the entire Home Assistant system'. It lists specific return fields, distinguishing it from sibling tools like domain_summary_tool which dives into specific domains.

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?

The 'Best Practices' section explicitly provides usage guidance: 'Use this as the first call when exploring an unfamiliar Home Assistant instance', 'Perfect for building context', and suggests using domain_summary_tool for deeper dives, effectively differentiating from alternatives.

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