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

Annotations already carry readOnly/idempotent/non-destructive, so the description earns credit for adding envelope behavior: missingIds for unavailable ids, warnings for capped includes, and the requirement to report truncation/pagination. The sentence "This read-only tool does not change data" largely restates the annotations, which keeps this from a 5.

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?

Purpose and usage are front-loaded, and the include-caps and alternatives are logically ordered. It is somewhat dense at seven sentences with some overlap between the second and third sentences, but almost every sentence carries actionable 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 5-parameter tool with nested objects, an output schema, and four annotations, the definition covers purpose, routing, id semantics, include caps, and error/truncation signals. Nothing an agent needs to invoke it correctly is missing.

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 coverage is only 60%, and the description compensates: it explains the ids omit/one/several semantics and the meaning of include (only extra details the user asked for, with documented caps). The workspaceId/account filter semantics, however, live primarily in the schema rather than the 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 opens with a specific verb+resource ("Read sender identities and optional account or voice details") and names the scope ("one stable collection envelope"). It also explicitly distinguishes itself from two siblings, get_campaigns for campaign guidance and get_workspaces for team/workspace settings, so an agent can route correctly without opening a schema.

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?

It gives an explicit trigger ("when the user needs to resolve an identity, LinkedIn account, or Google account to the human sender") and names alternative tools with the conditions that select them. The id-usage rules (omit = list, one = single record, several = several) further pin down invocation.

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