device_get_parameters

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

Discloses read-only nature and returns value/range/automation state, and conditional metadata. However, no annotations are provided, so the description bears full burden; it omits what happens when device doesn't match bundled schemas, error behavior, or authentication needs.

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?

Two concise, front-loaded sentences with no redundancy. First sentence states purpose and method; second adds usage context and return details. Every sentence earns its place.

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 two simple parameters and no output schema, the description provides reasonable context: returns basic parameter info and conditional metadata. Lacks clarification on error states, unmatched device behavior, and return structure, but adequate for a read-only inspection 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?

Schema description coverage is 0%, and the description only implicitly references parameters ('by track/device index'). It does not explain what track_index and device_index represent, their valid ranges, or how to obtain them, leaving significant gaps for an AI agent.

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?

Clearly states the tool is a read-only list of device parameters, using specific verbs and resource description. Distinguishes from sibling 'device_set_parameter' by mentioning 'use before automation or value changes'.

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?

Explicitly advises when to use ('before parameter automation or value changes'), providing clear context. Does not explicitly state when not to use or list alternatives, but the sibling set tool implies the contrast.

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