waha_get_chat_picture

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively adds valuable context beyond the input schema by specifying the caching behavior ('Uses 24-hour cache by default'), which is a key operational trait not captured in the schema. This helps the agent understand performance and data freshness implications.

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 perfectly concise and front-loaded: a single sentence that states the core purpose, followed by a second sentence adding crucial behavioral context. Every word earns its place with zero waste or 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?

For a simple read operation with no annotations and no output schema, the description provides adequate context about caching behavior. However, it doesn't describe the return value format (e.g., URL structure, error conditions), which would be helpful given the lack of output schema. The description is complete enough for basic use but has room for improvement.

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%, so the schema already fully documents both parameters (chatId format, refresh default). The description adds no additional parameter semantics beyond what's in the schema, but doesn't need to compensate for gaps. Baseline 3 is appropriate when the schema does the heavy lifting.

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 action ('Get the profile picture URL') and resource ('for a chat'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'waha_get_contact_profile_picture' or 'waha_get_group_picture', which serve similar functions for different entities.

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 provides implied usage context through the mention of '24-hour cache by default' and the 'refresh' parameter, suggesting when to use the cache vs. fresh data. However, it lacks explicit guidance on when to choose this tool over similar sibling tools (e.g., waha_get_contact_profile_picture for contacts vs. chats).

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