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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds genuinely non-obvious behavior: unentitled access returns the first 5 rows plus locked.count/locked.by_type and never the rows, contact values and decision-maker names are stripped to types and counts, and every answer discloses withheld data in entitlement/locked. That is exactly the kind of behavioral disclosure structured fields cannot convey.

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 core behavior and the two query directions are front-loaded, and the scoping details are compact. The closing entitlement/pricing block is several sentences long and partly promotional, though it does carry real access constraints.

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-value burden and does so well: it states that dfx:isi: ids are returned for both sides and describes the shielded fields. Gaps remain around pagination (cursor/limit interplay, max 50) and the unexplained rank_for_sponsor reference.

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 50%, and the description covers sponsor/provider (name or dfx:isi: id), family values and the meaning of rank_for_sponsor. However, rank_for_sponsor does not appear in the input schema at all, and limit, min_deals and cursor get no explanation in either the description or the schema, so it only partially compensates for the coverage gap.

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 resource (provider↔sponsor pairs from announced independent sponsor transactions) and the two directions of the query, so an agent knows precisely what it returns. It stops short of differentiating against close siblings such as search_sponsor_capital_providers, rank_service_providers or get_service_provider, which is the only thing keeping it from a 5.

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 explicitly states the two invocation modes ('give a sponsor ... or give a provider ...') and how family and rank_for_sponsor qualify the result, which is clear contextual guidance. It never says when not to use it or which sibling to prefer, and with many overlapping sponsor/provider tools in the list that omission matters.

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