wavexis_reload

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

The description states the action and return status but does not disclose behavioral traits like possible state loss, scroll position reset, or error conditions. Annotations are not contradictory but add little.

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 short and front-loaded with the core action. The args/returns block is structured but could be trimmed since schema covers parameters.

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 an output schema present, the return info is sufficient. However, the description lacks explanation of how 'current page' relates to the session parameter, and potential failure modes are not mentioned.

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 adds minimal value beyond the schema: it mentions 'ignore_cache' which is already described in the schema. No explanation for 'session_id' is given, and schema coverage is low.

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 'Reload the current page' uses a specific verb and resource, clearly differentiating it from sibling tools like wavexis_navigate, wavexis_back, and wavexis_forward.

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 reload versus alternatives, such as after page updates or when wanting to refresh. No exclusions or context are given.

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