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

No annotations exist, so the description carries the full behavioral burden. It does disclose real traits beyond the schema — buyer deduplication, capability verification of suppliers, sequential external-source execution, targeted supplier recovery, and a deployment gate — which is meaningful context. But it omits permissions, rate limits, side effects, and reversibility, and the dense phrasing leaves the actual behavior ambiguous.

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?

It is a single front-loaded sentence with the purpose first, which is good structure. But it crams seven dense, comma-jammed clauses into one run-on line without prioritization, making it hard to parse which traits matter most.

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 three-parameter orchestration tool with no annotations, no output schema, and 0% parameter documentation, the description is too thin. It gestures at internal behaviors but leaves the agent without the parameter guidance or prerequisite/permission details needed to invoke it correctly.

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 0% and none of the three parameters (limit, queries, buyer_limit) are explained in the description or schema. The phrase 'across multiple buyer-demand families' loosely suggests the queries parameter and the 'ranked' wording loosely suggests limit/buyer_limit, but no syntax, format, or meaning is given, so the description fails to compensate 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?

It states a specific verb ('Build') and resource ('ranked portfolio across multiple buyer-demand families'), so the core purpose is inferable. However, the term 'economic opportunity portfolio' is jargon-heavy and the description gives no hint about how it differs from siblings like build_portfolio_conversion_queue or discover_buyer_demand, which share the same vocabulary.

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?

There is no explicit when-to-use guidance and no named alternative. An agent cannot tell from this text when to prefer this tool over build_portfolio_conversion_queue or discover_buyer_demand, nor what preconditions must hold. The clause 'no named-counterparty deployment gate' hints at a policy but is not framed as usage guidance.

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