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

Annotations cover the safety profile (readOnly/idempotent/non-destructive), but the description adds real behavioral context: the source and sample of the history flags (7,169 bookings, 2019-2026), the effect sizes, and the honest caveat that they separated risk only weakly out of sample. That tells the agent how much weight to place on the flags, going beyond anything structured.

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 purpose is front-loaded, but the bulk is a dense run-on enumeration of return fields that reads as a wall of text rather than tight prose. It is informative yet heavier than necessary, so it lands below the concise ideal.

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 return values, and it does so thoroughly — field-by-field including bouts pulled from the card. It is nearly complete for a data-heavy tool; only the when-to-use framing is thin.

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%, so the baseline is 3. The description adds no extra meaning to level/limit/fighter beyond the schema, which already defines 'flagged' as everything except Clear. Baseline 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 (UFC fighters booked in the next 14 days) and enumerates the exact data returned — watch level, slate lock, DK/FD status, injury news, odds movement, etc. It is clearly distinguishable from siblings like invoke_mma_late_changes or invoke_mma_odds, so an agent can tell what this tool is without opening the 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?

Usage is only implied by the content described; there is no explicit 'use this when' statement and no routing against the neighboring invoke_mma_* tools (late_changes, odds, matchups). The one interpretive note — that history flags are context not a forecast — guides reading results rather than choosing this tool.

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