waha_get_profile_picture

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read operation by the word 'Get', but says nothing about what happens for contacts without a picture, whether group IDs are accepted in the same field, permissions, or failure behavior. An output schema exists so return shape is partly covered, but the behavioral surface is still largely undisclosed.

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?

A single, front-loaded sentence with no filler. It is appropriately sized, though its brevity is partly the cause of the missing session semantics rather than a model of efficiency.

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 tool is a simple read with an output schema, so the description does not need to explain return values. However, with no annotations at all and a required 'session' parameter left undefined, an agent could not confidently invoke it without guessing at the session argument.

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 0%, so the description must explain both parameters. It partially helps by indicating the identifier can be a contact or a group, but 'session' — a required parameter — is completely unexplained with no hint about whether it is a session name, ID, or default.

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 gives a specific verb and resource: retrieve the profile picture URL for a contact or group. This is unambiguous and clearly distinct from siblings like waha_get_me or waha_get_chat, though it does not explicitly name those alternatives.

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?

There is no statement of when to use this versus alternatives, no preconditions, and no exclusions. The only hint is that the target may be 'a contact or group', which does not tell the agent anything about selection criteria.

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