waha_get_contact_about

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states only that the tool retrieves a value, but gives no information about error handling, return format, authentication requirements, or side effects. For a read operation, this is minimal and lacks crucial details an agent needs.

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, concise sentence that communicates the tool's purpose without any unnecessary words or fluff. It is appropriately sized for a simple getter and front-loads the main information.

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?

With no output schema, the description should explain the return value and any error behavior. It only states what the tool does, leaving the agent guessing about the response structure, null handling, or prerequisites. The description is insufficiently complete for a one-parameter tool.

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 provides no description for contactId, and the tool description does not explain the expected format or meaning of the parameter. With 0% schema coverage and no compensation from the description, the agent has no information to construct a valid call.

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') and the specific resource ('the 'About' status of a contact'), distinguishing it from sibling tools like waha_get_contact, which presumably returns full contact details. The purpose is unambiguous and well-scoped.

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 implies usage when the About status is needed, but it does not explicitly state when to use this tool versus alternatives such as waha_get_contact. There is no mention of exclusions or context, so the agent must infer usage from the tool name and description.

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