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

The annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is largely covered. The description adds two genuinely useful points beyond that — the source is the linked phone and 'No manda nada' reassures the agent that importing does not message any contacts despite the open-world hint. It still omits how long the import takes, whether it runs synchronously, and what happens to previously imported conversations on a repeat run.

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 short sentences with no filler: the action and its purpose come first, and the non-sending clarification is placed last as a reassurance. Every clause 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?

For a one-optional-parameter import with no output schema, the description covers the essentials — what is fetched, where it lands, and which tool to call next — which is exactly what an agent needs to chain it correctly. The remaining gap is operational: nothing says whether the import is immediate or background, or what a failure due to a missing linked phone looks like.

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 description coverage is 100% and the brand_id field already carries guidance about asking the user when the brand isn't named, so the schema does the heavy lifting. The description does not mention brand_id at all or add any scoping meaning beyond it, which is the baseline 3 case for a single fully documented parameter.

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?

Names a specific verb and resource — pulling recent conversations from the linked phone into PilotControl — and points to the exact downstream sibling, list_conversations, that consumes the result. An agent can distinguish this import step from list_conversations (read) and from whatsapp_send_message (send) without opening any schema.

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?

Usage is implied rather than stated: the phrase 'para poder leerlas con list_conversations' tells the agent this is a prerequisite step before reading, which is useful sequencing guidance. But there are no explicit when-not conditions, no mention of what to do if the phone isn't linked, and no note on whether re-running is safe despite idempotentHint being set.

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