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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds essentially nothing beyond that and the schema: it does not mention defaults, clamping behavior, result ordering, or what a list response contains. That is a thin contribution for a read tool with no output schema.

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?

A single front-loaded sentence that covers both call modes with no filler. It is efficient, though the brevity leaves behavioral details unaddressed rather than merely compact.

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 six optional parameters, a nested MongoDB-style filter object, and no output schema, the description is adequate but thin. It explains the two modes but not the response shape, pagination semantics, or how the nested query object is interpreted, leaving the agent to rely entirely on the 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 description coverage is high (83%), so the baseline is 3. The description restates the id-versus-query split that the schema already documents, adding no extra meaning about sort syntax, field projection, or filter operators.

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 ('Find') and names the exact resource ('LimGameProfile records'), then distinguishes its two operating modes: single-record fetch by id versus filtered list. It is clear what the tool does, though it does not differentiate from siblings beyond the resource name itself.

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?

It gives useful mode-selection guidance (pass id for one record, query for a filtered list), which tells the agent how to choose between the two call shapes. It stops short of stating when to prefer this tool over related lookups or any preconditions, so the guidance is implied rather than explicit.

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