toggle_auto_describe_images

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

No annotations are provided, so the description carries the full burden. It adds behavioral context by stating the mutation effect and the scope of impact. However, it lacks details on side effects (e.g., what happens to existing analysis when toggled off) or any required permissions.

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 a concise two sentences that front-load the purpose and include a [mutation] tag. Every sentence adds value, no redundancy.

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 simple toggle nature and full schema, the description is fairly complete. It explains the tool's effect and scope. However, it omits mention of return values (no output schema) and potential impact on existing media analysis, which would enhance completeness.

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 coverage is 100% (both params described). The description adds value by expanding on the meaning of auto_describe_images (listing PDFs and audio), but does not address the second parameter auto_sentiment_analysis at all, leaving it ambiguous in the tool context.

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 it activates/deactivates automatic media reading (images, PDFs, audio) from WhatsApp. The verb 'Activar/desactivar' and resource 'lectura automatica de medios' are specific, and it distinguishes from sibling toggle tools by detailing the affected media types.

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 explains the scope (affects all AI systems: Piloto Automatico, WhatsApp Auto, respuestas manuales), providing clear context. However, it does not explicitly state when to use this tool versus sibling toggles like toggle_auto_sentiment_analysis, nor does it list exclusions.

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