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

With no annotations, the description carries the full behavioral burden, and it does disclose the return payload (public profile plus business email) and the two supported platforms. It says nothing about credit cost, rate limits, batch behavior, or what happens when no business email is found, so the safety/cost profile is opaque.

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?

A single front-loaded sentence with no filler; the payload is stated before the input forms. It is efficient, though the extreme brevity is partly the cause of the missing parameter and usage detail.

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 bulk enrichment tool with no output schema, no annotations, and 0% schema coverage, the description covers the essentials (what you pass, what you get back) but omits the find_email toggle, the 1000-item batch ceiling, and failure/empty-result behavior. Adequate but with clear gaps.

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%, so the description must compensate. It usefully defines the accepted formats for the 'profiles' array (profile URLs or @handles), but the 'find_email' boolean with default true is never mentioned, leaving half the parameters undocumented in both schema and description.

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 names the exact payload ('full public profile + business email') and the accepted input forms ('Instagram/TikTok profile URLs or @handles'), which is a specific resource+verb equivalent for a lookup/enrichment tool. It does not, however, explicitly distinguish itself from siblings such as find_creators or find_work_emails, so an agent must infer the boundary.

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?

Usage is only implied by the input format: an agent can infer it should call this when it already holds profile URLs or handles. There is no statement of when NOT to use it and no routing to alternatives like find_creators (discovery) or verify_emails, leaving the agent to guess the intended pipeline position.

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