contact_getAbout

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

With no annotations to rely on, the description carries the burden of behavioral disclosure. It explicitly states that the tool 'Returns null if you don't have permission to read their status,' which is a meaningful behavioral trait beyond the basic read operation. Additional details like error handling are absent, but this is a valuable addition.

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 contains a redundant first sentence ('Get the contact's current info') that essentially restates the tool's purpose, followed by a more specific but overlapping second sentence. One of these could be removed without losing information, and the first sentence is vague and unnecessary.

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 getter with no output schema, and the description covers the core action and a key permission-related edge case. However, it does not explicitly state the success return value (the about string), leaving that to inference. For a tool with this simplicity, the description is minimally adequate but not fully complete.

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 already provides 100% coverage, clearly describing both contactId and sessionId with examples. The description adds no parameter-level meaning, so the baseline score of 3 is appropriate.

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 tool retrieves a contact's 'about' info, which distinguishes it from sibling getters like contact_getProfilePicUrl or contact_getCommonGroups. However, the opening sentence 'Get the contact's current info' is vague and could imply broader data, slightly muddying the focus.

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 no guidance on when to use this tool versus the many sibling contact getters, nor does it mention any alternatives or exclusions. Usage is only implied by the tool name and the mention of 'about' info.

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