auto_capture_firebase_script

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

No annotations provided. Description discloses the tool outputs a script, modifies clipboard, and is non-destructive. Assures no manual digging, but does not detail side effects or permissions. Still reasonably transparent.

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?

Description is about 4 sentences, front-loaded with purpose, step-by-step, no wasted words. Highly concise and structured.

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?

No output schema, but description explains the output (script) and what to do with it. Complexity low, no parameters. Complete guidance for the intended use case.

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?

No parameters. Rule states baseline 4 for zero parameters. Description does not need to add meaning beyond schema, which 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?

Description clearly states the tool retrieves a browser-console script for auto-extracting 3 Firebase fields to enable Workflow Builder. It distinguishes from siblings by specifying integration with setup_ghl_mcp and enable_workflow_builder.

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 step-by-step instructions: run, copy script, paste in Chrome DevTools Console, press Enter, result in clipboard, then paste into another tool. Clearly indicates when to use (no manual IndexedDB digging). No explicit sibling differentiation but context is clear.

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