setup_camoufox

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

Even though no annotations are provided, the description discloses the main behaviors: it runs pip install and python -m camoufox fetch, is a no-op if already installed, and returns current status. It doesn't detail potential side effects or the exact meaning of 'force', but it gives a solid overview of the tool's 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 three concise sentences, front-loaded with the purpose, and every sentence adds useful information. There is no wasted wording, and the structure is logical: purpose, mechanism, conditional behavior.

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?

The description covers the tool's operation and return type, but it omits the meaning of the 'force' parameter, which is a significant gap for an otherwise simple tool. The output schema exists, so return values are handled structurally, but the parameter gap makes the description incomplete.

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 description doesn't explain the 'force' parameter at all, and the schema provides no description either. Since schema description coverage is 0%, the description should compensate, but it doesn't. The agent would have to guess what 'force' does based on the title alone.

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's function with a specific verb ('Ensure') and resource ('Camoufox stealth browser installed'). It distinguishes itself from sibling tools (web_search, fetch_page) by focusing on setup/installation, and includes key behaviors like idempotency and status return.

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 implies when to use it: any time the Camoufox browser is needed, it ensures it's installed. It doesn't explicitly mention alternatives or exclusions, but the sibling tools are unrelated, making the context clear. It could have been more explicit about calling it before other tools, but the implied usage is sufficient.

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