Mhs Read

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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=false. The description does not explain why a tool named and described as 'Read' is not read-only, nor does it detail side effects, authentication needs, or rate limits. The phrase 'retain independently generated image bytes' hints at a storage side effect but is ambiguous.

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?

Single sentence with no wasted words, front-loaded with the primary verb 'Read'. However, the second clause about retaining image bytes is vague and could be clearer.

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 three required parameters, a nested object, and rich schema/annotations/output schema, the description should clarify when to use this versus mhs_write and what 'retain' means. It leaves those gaps, making it incomplete for reliable tool selection.

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 schema already documents device_id, capability, and params. The description adds no parameter-level detail, but baseline is 3 when the schema carries the load.

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?

States a specific verb 'Read' and resource 'declared simulated sensors', plus a secondary operation 'retain independently generated image bytes'. It does not differentiate from sibling tools like mhs_write or mhs_meta_info, but the core read purpose is clear.

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?

No explicit when-to-use, prerequisites, or alternatives are provided. The only usage hint is implicit in 'declared simulated sensors' and 'retain image bytes', but there is no guidance on when to choose this over mhs_write or how to obtain capability via mhs_meta_info.

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