refresh_parameter

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

Discloses asynchronous behavior, queuing of task, and CPE contact dependency. Annotations indicate destructiveHint=true, but description does not elaborate on destruction; still, the mutation nature is clear.

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?

Well-structured with sections for purpose, usage, limitations, and example. Slightly verbose but every sentence adds value. Could be more concise.

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?

Complete for a tool with two simple parameters. Includes return value description (raw JSON), important limitations, and an example. No output schema needed; this covers the agent's needs fully.

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 100%, but description adds valuable context: device_id format (OUI-ProductClass-SerialNumber), where to obtain valid IDs, and multiple parameter path examples. Enhances understanding beyond 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?

Description clearly states the tool requests a CPE device to report a specific TR-069 parameter via GenieACS, distinguishing it from siblings like get_parameter, set_parameter, and reboot_device. The verb 'refresh' and target 'parameter' are specific.

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?

Explicitly states when to use (need up-to-date reading) and includes limitations (asynchronous, one parameter per call, full dotted path). Does not explicitly contrast with alternatives, but the context is clear.

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