refresh

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

No annotations are provided, so the description carries the full burden. It discloses that the operation is a forced refresh, implying it may be resource-intensive or override caching. However, it does not mention side effects like whether states are guaranteed to change, if the operation is blocking, or any required permissions or error conditions.

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, concise sentence that starts with the action ('Force refresh') and immediately specifies the target. There is no redundant or unnecessary wording.

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 no-parameter tool, the description is fairly complete: it identifies the operation, scope, and forcefulness. However, it lacks any mention of return values or potential side effects, which would be helpful given there is no output schema. Still, the description is adequate for a straightforward refresh action.

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 tool has zero parameters, and schema coverage is trivially 100%. The description adds meaning by clarifying the exact scope of the refresh (Matter bridge and logical bridges), which is necessary given there are no parameters to configure.

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 ('Force refresh') and the scope ('all device states from Matter bridge and logical bridges'). This is specific and distinguishes it from sibling get/set/control tools, which are about querying or modifying individual devices.

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?

The context is implied: use this when you need to force a refresh of all device states. However, no explicit alternatives or exclusions are mentioned, such as when to use get_sensor instead of refreshing everything. The guidance is not misleading, but it lacks direct comparison to other tools.

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