volume

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

No behavioral details beyond the action name. Doesn't disclose side effects (e.g., mute toggling), reliance on TV state, or feedback. No annotations to compensate.

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?

Very concise at two words, but oversimplifies. Could be expanded to include usage context without becoming verbose.

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?

With no output schema and only half the parameters described, the description fails to cover basic behavioral aspects like whether volume wraps around or if mute is persistent.

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 'steps' parameter has a schema description explaining its purpose, but the 'action' enum lacks description. The tool description adds no additional meaning for either 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?

Clearly states the verb 'Adjust' and resource 'TV volume', making it distinct from siblings like change_input or power. However, it doesn't specify that it controls TV volume specifically, which is inferred but could be more explicit.

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 on when to use this tool versus alternatives like send_key for volume. The description only states what it does, not when it's appropriate.

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