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

With no annotations, the description carries the full burden and does well: it discloses the cost ($0.15), the billing source and its constraint (paid from existing clink shop credits, new top-ups paused), and that failed/empty calls are free — all decision-relevant behavior. It also honestly scopes the contact data as 'emails actually found on their site/bio', implying no fabrication. It does not state whether the lookup is live or cached, nor typical latency.

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?

One dense but front-loaded paragraph: purpose first, then return contents, then pricing. The long enumeration of card fields is justified because no output schema exists, and the cost/payment caveat is placed last where it belongs. Slightly overstuffed for a single sentence, but nearly every clause carries 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?

For a paid external-call tool with no annotations and no output schema, the description supplies the two things that matter most: the shape of the return value and the billing/failure behavior. Gaps are minor — no rate limits, no statement on invalid or suspended handles, and no comparison to the adjacent x_profile/x_leads_deep tools.

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?

There is a single required parameter with 100% schema description coverage, including an example ('naval'), so the schema fully documents it. The description adds no syntax or format detail beyond the schema, which is the expected baseline-3 outcome 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?

States a specific verb and resource — 'X/Twitter person lookup' — and then enumerates exactly what the returned card contains (name, role, company, contact routes, stats), so an agent knows precisely what it gets. It frames the audience ('lead/recruiting/sales agent'), which implicitly separates it from the raw x_profile sibling, but never names that sibling, so differentiation is inferred rather than stated.

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 mention of 'a lead/recruiting/sales agent' implies the intended use case and the $0.15-per-call / free-on-failure pricing gives a concrete decision input. However, there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. x_profile for a cheap raw profile, x_leads_deep for bulk), leaving the agent to guess which X-person tool to pick.

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