tor_refresh

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

The description does not disclose any behavioral traits beyond what the annotations already specify. Refresh may trigger page reloads that discard unsaved form data or re-send POST requests, but this is not mentioned. With annotations already stating readOnlyHint=false and destructiveHint=false, the description adds no extra context about side effects or state changes.

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, front-loaded sentence that conveys the exact action with no extraneous information. Every word earns its place, and the structure is appropriately minimal for a tool of this simplicity.

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 tool's low complexity (no parameters, simple action), the description is largely complete. It clearly states what the tool does, and the output schema exists to handle return value expectations. However, it lacks mention of edge cases like unsaved data or timing, so it is not a perfect 5.

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 the schema is empty with 100% coverage. Per the baseline, a description is not required to compensate for missing parameter info. The description correctly omits parameter details since there are none, making it appropriate for the 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?

The description 'Refresh the current page.' uses a clear, specific verb and resource. It distinguishes the tool from siblings like tor_navigate, tor_back, and tor_forward, which have different navigation actions. It unambiguously states the tool's function.

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 description offers no guidance on when to use this tool versus alternatives. It does not mention scenarios where a refresh is preferable to re-navigating, nor does it note any prerequisites or conditions. The agent receives no contextual help for tool selection.

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