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

With no annotations provided, the description takes on the full burden of behavioral disclosure. It explains the matching fallback (id, then case-insensitive name), the aggregation of deal count and value, and how unmapped deals are handled. This provides good transparency into the tool's 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 is extremely concise, consisting of two sentences that cover the core functionality, matching logic, and handling of unmapped deals. Every sentence adds value, and the structure front-loads the main purpose.

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?

Given that there is no output schema, the description provides sufficient context: it mentions ranking by deal count or value, and the inclusion of unmapped_deals. It could be more explicit about the output structure, but for a low-complexity tool with two parameters, it is reasonably complete.

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 100%, so the schema already describes both parameters (limit, sort_by) and their allowed values. The description does not add new semantic meaning beyond what is in the schema, so the baseline score 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 clearly states the tool ranks taxonomy segments by M&A activity, mapping deals to segments. It uses specific verbs ('ranks', 'mapping', 'aggregating') and identifies the resource ('taxonomy segments'). While the purpose is clear, it does not explicitly differentiate from sibling tools like get_ma_activity_summary or get_segment_leaders.

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?

The description implies usage for analyzing M&A activity concentration across segments, and explains the matching logic and handling of unmapped deals. However, it does not provide explicit guidelines on when to use this tool versus alternatives, nor does it state when not to use it.

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