Inspect a saved lead matchup

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

The readOnlyHint annotation already establishes the read-only safety profile, and the description doesn't contradict it. It adds context by saying the data is bounded and persisted, which distinguishes this from live evaluation or replay-based data, but it doesn't describe pagination/offset behavior or any other operational details.

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?

One short, front-loaded sentence with no redundant filler. It earns its keep by stating verb, resource, and provenance in a compact form.

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?

Despite the output schema and read-only annotation covering return and safety aspects, the tool has nine parameters with no param-level descriptions and no usage guidance. An agent would still need to infer which identifiers/options to supply and what 'bounded' means in practice.

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 0%, so the description needed to compensate for nine undocumented parameters, but it only loosely hints at them with 'lead-state' and 'bounded'. Analysis_id, user_lead, opponent_lead, offsets, and limit are never explained or mapped to the retrieval behavior.

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 uses a specific verb ('Retrieve') and identifies the resource ('bounded lead-state details') and source ('persisted team evaluation'), so an agent can tell this is a read-style lookup rather than an analyze/evaluate operation. It is not fully explicit about what 'bounded lead-state details' means, and it doesn't name a sibling alternative, so it stops short of a 5.

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?

No guidance is given about when to use this tool instead of siblings like vgc_team_evaluate, vgc_replay_get, or vgc_meta_query. A mention that this is for inspecting previously persisted evaluations would have been useful, but the description leaves the routing decision to inference.

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