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

Annotations already cover read-only, idempotent, and open-world behavior. The description adds valuable behavioral context beyond annotations by disclosing endpoint-dependent authentication: api_key is optional on the public endpoint but refused when missing on /mcp/mcp. This helps the agent make correct runtime decisions.

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 compact and front-loaded with the core purpose. The second sentence adds an essential invocation nuance without waste. Every sentence earns its place.

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 an output schema present, the description need not restate return values, and it provides the key endpoint-specific authentication caveat. It is slightly incomplete in not guiding tool selection among siblings, but for a simple read-only get-by-ID operation, the necessary calling context is largely covered.

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%, and the description does not explain domain_id beyond its self-evident name. However, it does add meaningful semantics for api_key by explaining the endpoint-specific requirement, which is not visible in the schema. This partially compensates for the lack of schema descriptions.

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 clear verb and resource: "Get domain details including entity pool and competition list." This identifies the tool's function and distinguishes it from more specific list tools like list_competitions, though it does not explicitly name a sibling or contrast behavior.

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 gives no guidance about when to use this tool versus alternatives such as aimrank_list_domain_entities or aimrank_list_competitions. The api_key note is about endpoint authentication, not tool selection, so the usage context is absent.

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