Extract raw authentication material

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

With no annotations, the description carries the full burden. It discloses key traits: 'Requires explicit confirmation and returns secrets.' However, it does not mention side effects, failure modes, or whether the operation is read-only, leaving some ambiguity for a security-sensitive tool.

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 concise, action-fronted sentences with no filler. Each sentence earns its place: the first defines scope, the second adds critical behavioral and return information.

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?

For a tool with 4 parameters, no annotations, no output schema, and a security-sensitive purpose, the description is insufficiently complete. It covers purpose and one behavioral trait but leaves parameter semantics, output format, error handling, and usage context underspecified, increasing the risk of misuse.

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%, and the description adds minimal parameter meaning. 'Requires explicit confirmation' hints at the 'confirmed' boolean, but the required 'sessionId', 'targetSessionId', and 'timeoutMs' are completely unexplained, making correct invocation difficult.

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 a specific verb 'Extract' with a precise resource: 'authentication headers and associated cookies' from 'captured Raw events'. This differentiates it from sibling tools like network_get_response_body or browser_network_poll.

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 explicit guidance is given on when to use this tool versus alternatives. There are no exclusions, triggers, or references to sibling tools. The only implication is that it is used for extracting auth material, but no decision framework is provided.

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