read_registers

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

Description implies a read-only operation ('dump') but does not explicitly state safety or lack of side effects. With no annotations to fill the gap, the description partially covers behavioral traits but could be more explicit.

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?

Extremely concise single sentence with examples, front-loaded verb 'Dump' immediately conveys action. No wasted words.

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?

Tool is simple with no parameters and has an output schema. The description is sufficient: it states what registers are included. No further explanation needed given the context.

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?

No parameters, so schema coverage is 100% trivially. The description adds no parameter info (none needed), meeting the baseline for zero-parameter tools.

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 dumps all CPU registers with a specific list of examples (r0-r15, pc, sp, lr, xpsr). Distinguishes from similar sibling 'read_register' (singular) and other tools by implying bulk read.

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 guidance on when to use this tool vs alternatives like 'read_register' or 'list_peripheral_registers'. Agent must infer from the description that this is for a full dump of core registers, but no when-not or prerequisites mentioned.

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