read_arbitrary

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 still contributes useful behavior context by fixing the read size at all 2048 samples (i.e., no partial reads) and constraining the slot domain, but it says nothing about return format, units, or error behavior for an out-of-range slot.

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?

One front-loaded sentence that conveys action, scope (all 2048 samples), and the parameter domain with zero padding. Every clause 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 a simple single-parameter read whose annotations already cover safety, the definition is adequate but incomplete: with no output schema, the description should describe what the 2048 samples look like on return, and it offers no error or boundary behavior.

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 0%, so the description must carry the parameter meaning, and it does: it identifies the single arg as an arbitrary-waveform slot with valid values numbered 1..60. That domain constraint is meaningful semantics absent from the bare integer schema.

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?

Specific verb (Read) plus resource (samples from an arbitrary waveform slot) with the exact sample count (2048) and slot domain. An agent can immediately distinguish this read operation from the sibling upload_arbitrary without opening a schema.

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?

Usage is only implied: the tool reads arbitrary-waveform data, and the counterpart upload_arbitrary is visible among siblings. The description never states when to reach for this versus upload_arbitrary or how it fits a read-after-upload workflow, so guidance is inferred rather than given.

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