get_cookies

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

The description discloses the two retrieval behaviors (all or specific cookie). Annotations already provide readOnlyHint=true and idempotentHint=true, so the safety and idempotency are clear. The description adds value by explaining the conditional retrieval, but could go further by mentioning that no modifications occur.

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 two sentences, front-loads the core functionality, and wastes no words. Every sentence serves a purpose.

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 simplicity (one optional parameter, no output schema), the description adequately covers what it returns and when to use it. It does not detail the return format, but this is reasonable for a straightforward read operation.

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 input schema has 100% coverage with a clear description of the 'name' parameter. The description reiterates 'by name' but does not add new meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 tool returns all cookies or a single cookie by name. 'Get' verb with 'cookies' resource is specific, and the optional parameter distinguishes retrieval of all vs. one. Among siblings like delete_cookies and set_cookie, this read operation is clearly distinct.

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 explicitly advises using the tool to verify auth state, session tokens, or feature flags after login flows. This gives clear context for when it's appropriate. However, it does not mention when not to use it or point to alternatives, though the use cases are well-covered.

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