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

Annotations already declare readOnlyHint=true and openWorldHint=false, covering the safety profile. The description adds useful behavioral context: it discloses the data sources (Warcraft Logs, M+ leaderboards) and specifies return values (modal build string, sample size, per-choice pick frequencies), which are not captured by annotations.

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?

Three sentences, front-loaded with purpose, then usage instructions, then return values. No wasted words; every sentence adds necessary information.

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?

The tool has 4 parameters (3 required), low schema coverage, and no output schema. The description adequately covers purpose, content_name/difficulty usage, and return values, but lacks detail on class/spec formats and when difficulty is optional versus required. For an agent to call it correctly, more parameter semantics would be helpful.

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 only 25% (only content_name has a description), so the description must compensate. It does explain content_name usage ("All Bosses", "All Dungeons") and clarifies difficulty values for general builds. However, it does not explain the expected format for class and spec parameters, leaving a gap.

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 (Get), resource (importable loadout), and scope (players actually ran to kill a raid boss or clear an M+ dungeon), with data sources (Warcraft Logs, M+ leaderboards). Distinguishes from siblings like generate_build (AI-generated) and decode_build (decoding) by emphasizing real-world aggregated data.

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 clear guidance on how to use the content_name and difficulty parameters for different content types, but does not mention when to use this tool versus alternatives such as generate_build or get_talents. Usage is implied by the described use case rather than explicitly contrasted with siblings.

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