wavexis_cookie_get

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

Annotations already declare readOnlyHint true and destructiveHint false. Description adds that side effects are none and reads cookie state, aligning with annotations. It also describes return format, which provides extra behavioral 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?

Two concise sentences with bullet-like side effects and returns. Front-loaded with action 'Retrieve a single cookie'. No superfluous text.

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 annotations covering safety and output schema for return, description is mostly complete. Minor gap: session_id parameter not explained, but it is likely a common context parameter across tools.

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 description coverage is 0%. Description clarifies name as main identifier and mentions optional path/domain, adding meaning over schema. However, it does not explain the session_id parameter, which is required. Baseline 3 with partial compensation.

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?

Description explicitly states 'Retrieve a single cookie by name (and optional domain/path)', clearly identifying the tool's specific verb and resource. It distinguishes from the sibling wavexis_cookie_list, which is for multiple cookies or broad filtering.

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?

Description proactively directs to wavexis_cookie_list when multiple cookies or broad filtering are needed, providing clear when-to-use and when-not-to-use guidance.

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