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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered; the description adds genuinely new behavior: parallel-safety, an upstream cost of 1-3 calls, and the UFC-specific client re-rank ordering (exact name > multi-token > nickname). It does not cover rate limits or error/degradation behavior, so it is good but not exhaustive beyond the annotated baseline.

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?

Sectioned with headers, front-loaded with purpose before rules, and every block (when-to-use, prefer/avoid, UFC ranking note, example) carries distinct information. Slightly verbose in places — the UFC ranking rule is restated across the 'when to use' bullet and the standalone block — which keeps it from a 5.

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 6 parameters, a required game, 100% schema coverage, and an output schema present, the description supplies exactly the missing pieces: selection guidance, alternatives, ranking semantics, parallel safety, and cost. Return-value documentation is correctly delegated to the output schema.

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 baseline is 3; the description earns above baseline by explaining that 'q' triggers ranked UFC results and that 'Jon Jones' should return jon-jones first rather than a generic P4P list, and by showing a concrete combined-parameter example. It does not add meaning for cursor or activeOnly beyond the schema.

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?

States a specific verb and resource set ('Browse/search teams, players, tournaments, events, fighters') plus a scope qualifier ('with type filter and pagination'). It explicitly distinguishes itself from resolve_entity, team_profile, and player_profile, so an agent can route without opening any 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?

Provides explicit when-to-use bullets (typeahead, list queries, exploring without committing to an ID), explicit when-not ('fetching a known entity profile'), and names the two alternatives with the exact condition that selects each ('user wants a list' vs 'chaining one name into a profile tool').

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