domotz_get_agent_overview

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

With no annotations, the description describes key behaviors: combining multiple data types and summarizing the device list (first 50 + total count) when there are over 50 devices. It notes the agent_id requirement. It does not mention read-only status or potential performance implications, but covers the main behavioral traits.

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 concise at 4 sentences, front-loaded with the main purpose, then adds details on content, usage, requirement, and a specific limitation. Every sentence is valuable and there is no redundancy.

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's simplicity (one parameter, no output schema), the description provides a good overview of what is returned (agent details, device list, uptime) and a behavior limit (summary for >50 devices). It could mention if pagination is needed but is otherwise complete.

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 schema already fully describes the single parameter agent_id with a description. The description reiterates the requirement but adds no new semantic information beyond what is in the schema, so it meets the baseline without adding extra value.

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 specifies the verb 'Get', the resource 'collector overview', and the scope 'single call' combining agent details, device list, and uptime. It distinguishes itself from sibling tools like domotz_get_device_full_status which targets a single device, and separate tools for agents and devices.

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 description advises using this as a starting point when exploring a collector/site, providing clear context. It does not explicitly state when not to use or list alternatives, but the guidance is helpful.

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