cookie_export

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

No annotations provided. Description discloses output format (JSON array), location (~/.mcp-stealth/storage-states/), and compatibility. Does not mention whether it overwrites existing files or requires any particular permissions, but the operation is likely non-destructive. Adequate but could be more detailed about side effects.

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?

Extremely concise: two sentences. The first sentence states purpose, the second adds key details (format, location, compatibility). No unnecessary words.

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?

The tool has an output schema (not shown) which likely covers return values. The description covers format, location, and sibling alternative. However, it omits parameter semantics and any preconditions. Simple tool but missing parameter details reduces completeness.

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 2 parameters (filename, url) with 0% description coverage. The description provides no explanation of these parameters, leaving the agent to infer from names and context. This is a significant gap: the description must compensate for missing schema descriptions but fails to do so.

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 the verb 'Export' and resource 'cookies', and distinguishes from the sibling 'storage_state_save' by specifying 'Cookies-only (use storage_state_save for full session)'. It also mentions output format (JSON) and location.

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?

Provides explicit when-to-use guidance by comparing with storage_state_save for full session. Mentions compatibility with cookie_import/EditThisCookie/Playwright, giving context. Lacks explicit when-not-to-use scenarios but is clear enough.

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