Read an IIO attribute

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond the schema by explaining the '_available' attribute convention for discovering legal values, which is genuinely helpful for using the tool correctly.

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?

Three sentences with no filler: purpose, tool-routing guidance, and an important attribute discovery behavior. The most important information is front-loaded.

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 read-only escape-hatch tool with a 100%-covered schema and an output schema present, the description provides all needed decision-making and invocation context. openWorldHint supports its role as a general-purpose fallback, and the annotations cover safety.

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 100%, so the baseline is 3. The description adds extra semantic value by explaining how to find valid attribute names via sdr_list_devices and by describing how the '_available' suffix works, which directly enriches the 'attribute' parameter.

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 states a specific action ('Read any single IIO attribute by name') and clearly identifies the resource. Calling it 'an escape hatch for anything the other tools do not cover' differentiates it from a large sibling set without listing each sibling.

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?

It gives explicit guidance on when to use the tool ('escape hatch... anything the other tools do not cover') and points to sdr_list_devices for discovering valid attribute names. It does not name specific alternatives or state a concrete 'when not to use' condition, so it falls just short of a 5.

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