cdp_call

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

No annotations are provided, so the description carries full burden. It explains the session context (use_session parameter) but does not disclose potential risks like browser crashes or permission requirements. The examples imply safe usage but lack explicit warnings about destructive behavior.

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 relatively concise, front-loading the purpose and then explaining parameters and examples. Every sentence adds value, but it could be slightly more condensed without losing clarity.

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 has 3 parameters, no annotations, and an output schema exists (return values not required), the description covers all necessary usage information: parameter meanings, when to use vs siblings, and concrete examples. It is complete for an agent to select and invoke the tool correctly.

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?

With 0% schema description coverage, the description fully compensates by explaining all three parameters: method (domain.method format), params (JSON string with example), and use_session (boolean for context). Examples clarify parameter usage.

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 'Llama cualquier metodo del protocolo CDP directamente' (calls any CDP method directly), and then gives examples of actions without dedicated tools, distinguishing it from siblings like click, navigate, etc.

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 says 'Ejemplos de acciones que no tienen tool dedicada' (examples of actions without dedicated tool), guiding the agent to use this tool for CDP methods that are not covered by sibling tools. It provides concrete examples like drag & drop, file upload, device emulation.

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