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 only discloses the 3-credit cost. It does not state whether this is a read-only lookup, how enrichment behaves if a profile is not found, whether calls are idempotent, or what a successful/cached lookup returns.

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?

Two short sentences with zero filler, and the operational purpose is front-loaded before the cost note. It is terse to the point of under-specification, but nothing is wasted or buried.

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?

There is no output schema and no annotations, and five optional parameters mean the agent must guess how inputs combine and what the enriched payload contains. For a dual-purpose (find + enrich) tool with cost implications, the description omits too much to call it 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?

Schema description coverage is 100%, so all five parameters are already documented in the schema. The description adds no format hints (e.g., LinkedIn URL matching, name normalization) or guidance on which identifiers work best, so the baseline 3 applies.

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?

"Find and enrich professional profiles" gives a specific verb pair (find/enrich) and a clear resource (professional profiles), which distinguishes it from lookup siblings like companies or emails. It stops short of naming how it differs from adjacent tools such as search or scrape, so it is clear but not fully differentiated.

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?

No indication of when to choose this over siblings like companies, emails, or search, and no prerequisites or input-combination rules. The only usage-relevant signal is the credit cost, which hints at cost-sensitivity but does not guide tool selection.

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