domotz_get_device_full_status

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

With no annotations provided, the description carries full burden. It discloses that results are summarized if >50 items in any category and that it combines multiple API calls into one, indicating no destructive side effects. Could mention performance or error handling, but sufficient for safe invocation.

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?

Four concise sentences: purpose, components, usage guidance, requirement and behavior note. Front-loaded with key phrase. No unnecessary words, each sentence adds value.

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 simple parameters (agent_id, device_id) and no output schema, the description covers purpose, usage context, parameter requirement, and a behavioral note (summarization). Could mention error conditions or rate limits, but adequate for an AI agent to decide.

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?

Schema coverage is 100%: both parameters have clear descriptions in the schema. The description merely restates 'Requires agent_id and device_id' without adding new semantics. Baseline 3 is appropriate.

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 comprehensive device status in a single call' and specifies it combines 5 API calls (device info, status history, SNMP sensors, TCP sensors, alert bindings). This distinguishes it from sibling tools like domotz_get_agent_overview or domotz_search_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 provides clear usage guidance: 'Use this instead of making separate calls when you need a full picture of a device.' It implicitly contrasts with separate API calls but does not explicitly state when not to use it (e.g., if only one data type is needed).

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