post_contact

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

With no annotations, the description carries the full burden of disclosing side effects, permissions, or return behavior. It discloses none of these; it only names input fields and a required parameter. The mention of fields absent from the schema adds confusion rather than behavioral clarity.

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 text is brief, but brevity is not conciseness when it omits essential information. The structure front-loads parameter-like fragments and a fragment 'for a post,' which is confusing rather than efficient.

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 has one parameter, no annotations, no output schema, and no behavioral explanation. The description provides almost no context about the operation, its effects, or its inputs, making it impossible for an agent to invoke it correctly with confidence.

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%, and the description fails to clarify the meaning of post_id beyond the schema's own title. Worse, it references contactText, contactMobile, and shouldEnableWhatsApp, which do not exist in the input schema, actively misleading an agent about the parameters it can pass.

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 lists fields ({contactText, contactMobile, shouldEnableWhatsApp}) and says 'for a post,' but never states an explicit action verb like 'create' or 'update.' It reads more like a fragment than a purpose statement, leaving the tool's actual behavior ambiguous.

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 guidance on when to use this tool versus any alternative. The only hint is 'Required: post_id,' which is input syntax, not usage context. No sibling tools or exclusions are referenced.

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