wavexis_back

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

The description indicates it navigates back and returns a status, but does not disclose potential side effects (e.g., losing form data) or failure conditions. Annotations are present but add minimal context beyond the description.

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 extremely concise—two sentences plus a return value line—with no redundant or extraneous information.

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 navigation action, the description covers core functionality and return format but omits context about session prerequisites (e.g., an active session) and error handling.

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 only vaguely references 'Session reference parameters' without explaining the session_id parameter or how to obtain it. Schema coverage is 0%, so the description fails to add meaning beyond the schema's structural information.

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 'Navigate back in browser history,' which uses a specific verb and resource, and distinguishes the tool from siblings like wavexis_forward and wavexis_navigate.

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 implies when to use the tool but does not provide explicit guidelines on when to use it vs. alternatives, nor does it mention prerequisites or exclusions.

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