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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds that this is a third-party Forager call needing account credentials, but says nothing about what happens when no phone is found, credit consumption, or the response payload.

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 front-loaded sentence covering purpose, provider, and prerequisites, followed by an example call. The example partially duplicates the schema's own examples array, which is minor redundancy but still aids invocation.

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?

No output schema exists, so the description should indicate what comes back (a phone number string? null on miss?) and it does not. For a simple single-purpose read the definition is workable, but an agent cannot predict the return shape or miss behavior.

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 every parameter is already documented in the schema. The description only reiterates the two credential parameters and shows an example with linkedin_url; it does not explain the person_id alternative (schema-only detail) or add format/syntax meaning beyond the schema, so 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?

States a specific verb (find), a specific resource (a person's phone number), the input it derives from (LinkedIn profile URL), and the provider (Forager). No sibling in the list does phone lookup, so the boundary is clear without naming a competitor tool.

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 names the credential prerequisite (Forager account id and API key) and supplies a working example, which implies usage. It does not say when to prefer this over siblings like entity_profile or resolve_entity, nor mention the person_id alternative path or any exclusion such as rate/credit limits.

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