pet_wait_mem

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

The description reveals that the tool blocks and accepts hex/decimal values, but it does not disclose timeout behavior, error conditions, or any side effects. With no annotations, this is only partial disclosure.

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?

The description is a single sentence of 13 words, with the key verb placed first. Every word is necessary and there is no superfluous information.

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 the 4 parameters, lack of output schema, and no annotations, the description is insufficient for a complete understanding. Missing details on address format, value format, timeout behavior, and how blocking is implemented.

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?

The description implies the roles of 'addr' and 'equals' but does not clarify their formats (e.g., address representation, value as single byte or string). The 'session' and 'timeout' parameters are ignored, and schema coverage is 0%.

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 clearly states the action ('Block until'), the resource ('byte at addr'), and the condition ('equals the value'). It effectively distinguishes from siblings like 'pet_wait_break' and 'pet_wait_text'.

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 guidance is provided on when to use this tool versus alternatives, nor any conditions under which it should not be used. The description merely states the operation.

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