camofox_query_selector

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

No annotations exist, so description alone must disclose side effects. It only mentions input and output, not read-only nature, permissions beyond API key, or potential impacts. Lacks full behavioral context.

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?

Two concise sentences, front-loaded with core action, no fluff. Every part earns its place.

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?

Adequate for a simple 3-param tool with full schema coverage. However, lacks mention of output format or structure, which could help an agent understand what 'element details' means.

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 covers all 3 params with descriptions. The description adds 'return its element details or a specific attribute', but this is mostly redundant and does not significantly enhance meaning beyond schema.

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 verb 'Query' and the resource 'CSS selector in the live DOM', and distinguishes from sibling 'camofox_evaluate_js' by noting it avoids raw JavaScript.

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?

Explicitly states when to use: 'targeted inspection without writing raw evaluate_js', implying the alternative. No explicit when-not, but enough context for an AI agent.

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