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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds substantial context beyond them: exactly what an unentitled caller sees (first 5 rows in full plus locked.count/locked.by_type, never the rows), how much of a record is exposed (subject plus first 3 related names per section), that contact values and decision-maker names are never returned, and that withheld material is reported in `entitlement` and `locked`. This is unusually thorough disclosure of a non-obvious access model.

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?

The resource identity is front-loaded, which is good, but the body is a single sprawling colon-delimited enumeration followed by a long ACCESS block and a promotional line with a signup URL. The content is useful, yet the wall-of-text form makes the key facts harder to scan than they need to be.

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?

With no output schema, the description carries the return-shape burden and does so: it lists each section returned, the entitlement-truncation behavior, and the fields that are always suppressed. For a two-parameter lookup tool, nothing an agent needs in order to call 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 description coverage is 100%, so the baseline is 3, and the description adds provenance the schema lacks: the dfx_id is a dfx:isi:<uuid> sourced from rank_service_providers, and `name` is the fallback when no id is at hand. It does not say whether name is fuzzy-matched or what happens on ambiguity, so it is slightly above baseline rather than fully additive.

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 a specific resource (a law firm, bank, accounting or diligence firm as seen through the independent sponsor graph) and enumerates exactly what the record contains: deal counts, role mix, served sponsors, capital providers, named professionals, engagements, and dated signals. An agent can distinguish this from rank_service_providers (a ranked list) and search_service_provider_sponsors without opening the 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 tells the agent where the identifier comes from ('Give the dfx:isi: id from rank_service_providers or a name'), which is real routing guidance to a sibling tool. It does not state when to prefer this over search_service_provider_sponsors or what to do if multiple providers match a name, so it stops short of full when/when-not coverage.

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