get_all_cookies

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

No annotations exist, so description must fully explain behavior. It only says 'placeholder implementation', suggesting incompleteness, but fails to disclose what the tool actually does or its limitations.

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?

Very short, but the 'placeholder implementation' note adds necessary caveat while being somewhat vague. Could be more informative without adding length.

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 no annotations, no output schema, and a bare description, the tool is incomplete. It does not explain return values, behavior, or reliability.

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?

Input schema is empty with 0 parameters, and schema description coverage is 100%. Baseline for such cases is 3. The description adds no parameter-specific meaning but the schema is trivial.

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 states 'Get all cookies' which is a clear verb+resource, but the 'placeholder implementation' qualifier reduces confidence and clarity. It distinguishes from sibling tools which do not mention cookies.

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 on when to use this tool versus alternatives. No context provided about prerequisites or appropriate use cases.

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