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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds useful behavioral context: the tool is throttled, returns an AI-ranked recommendation, and is restricted by caller role. This goes beyond what the annotations alone provide without contradicting them.

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 three tight sentences: purpose, authorization/prerequisite, and throttling warning. Every sentence carries useful information and the most important context is front-loaded.

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 only two parameters, no output schema, and strong annotations, this description is complete enough for correct invocation. It states what is returned, who may call it, what input is needed and where to get it, and a performance caveat.

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?

Both parameters already have schema descriptions, so the baseline is 3. The description adds value by explaining that free_member_id comes from specific upstream tools and that locale controls the language of generated explanations, which the schema only partially implies.

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 a specific action and resource: an AI-ranked list of teams a free agent could join within the same event. It also adds meaningful scoping details (teamless participant, same event, owner/admin only) that distinguish it from generic team list tools.

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 tells the caller how to obtain the required free_member_id via event_free_agents or event_join_as_free_agent, and it gives an explicit permission boundary (owner or admin). It also warns against tight loops due to throttling, though it does not explicitly enumerate sibling alternatives or when-not-to-use conditions.

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