get_whatsapp_profile

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

With no annotations, the description must carry the behavioral burden. It describes the read operation and expected output contents but does not disclose potential errors, permission requirements, or side effects. The mention of 'sesion conectada' implies a prerequisite, which adds some transparency.

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 single long sentence that packs many details, which affects readability. It could be broken into bullet points for clarity, but it is not excessively verbose.

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 no output schema, the description covers the main return contents. However, it omits error handling, format details, and does not differentiate from similar tools like 'get_whatsapp_connection_status' adequately.

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 input schema has 100% description coverage for the single parameter 'session_id', which already explains its purpose. The tool description adds no new semantic information beyond reinforcing that the session must be connected.

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 'Obtiene' (gets) and the resource 'perfil de WhatsApp', and lists specific sub-elements (name, photo, status, business info), distinguishing it from sibling tools like 'update_whatsapp_profile' or 'get_whatsapp_connection_status'.

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 does not provide explicit guidance on when to use this tool versus alternatives. It only implies usage when a connected session exists, but no when-not or alternative tool comparisons are given.

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