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

Annotations already declare readOnlyHint, openWorldHint false, and destructiveHint false, but the description adds meaningful semantics: searches may be wider than the TAM but never narrower, Subscription applies the TAM to returned results, non-carried criteria are listed with reasons, and defined is false when no TAM exists. It also explicitly says reading calls no provider and changes nothing, reinforcing the safe-read behavior.

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 description front-loads the core purpose, but it is a dense, run-on block with nested clauses and parentheticals that make it hard to parse. Most clauses contribute domain nuance, but the structure is not concise and could be broken into clearer sentences.

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 burden of explaining the return semantics: provider searches, wider-but-never-narrower behavior, non-carried criteria categories, and the defined flag. It is conceptually complete for a complex read-only TAM tool, though the exact return shape remains somewhat abstract.

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%, and the single connection_id parameter is documented in the schema as the CRM connection with a call-first instruction. The description adds no further parameter-level meaning, so the baseline of 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?

The description states a specific resource and perspective: the provider searches that a connection's TAM compiles to outward for Subscription. It is distinguishable from get_tam, but the dense domain jargon and lack of an explicit sibling comparison keep 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?

No explicit guidance is given on when to use this tool versus get_tam, list_search_criteria, or other TAM-related siblings. The line about reading calling no provider is behavioral, not usage guidance, and the schema note to call list_crm_connections first is not in the description.

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