wavexis_cookies_get

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

Describes side effects: launches browser backend, navigates if url provided, and declares read-only with respect to browser state. This aligns with annotations (readOnlyHint, idempotentHint, destructiveHint false) and adds useful context.

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 front-loaded with purpose, then alternative tools, side effects, and return format. Each sentence is efficient and necessary, with no fluff.

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 complexity and presence of annotations and output description, the description is mostly complete. It covers purpose, alternatives, side effects, and return format. However, it does not explain parameters like backend, headless, session_id, but these are documented in the schema.

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 has 0% description coverage, but the description mentions the url parameter's effect ('navigates to url if provided') and implies session context. However, it does not add significant meaning beyond the schema's existing parameter descriptions.

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 'Retrieve all cookies for the current page context' with a specific verb and resource. It distinguishes from siblings by mentioning wavexis_cookies_set and wavexis_cookies_clear for different operations.

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 alternatives: 'Use wavexis_cookies_set to add a cookie, or wavexis_cookies_clear to remove all cookies'. Provides clear context for when not to use this tool.

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