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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, but the description adds substantial operational context beyond them. It discloses that each call is an uncached Jagex read requiring no credentials, that HTTP defaults to 60 requests/IP/minute, that callers should wait for Retry-After after a 429, and that totals count the category rather than the letter. It also clarifies error semantics and price-lag behavior.

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 front-loaded with the core purpose and sibling routing, then uses compact bullets for discovery, parameter examples, pagination, count semantics, and rate limits. Every bullet adds operational value, and there is no redundant restatement of the schema or annotations.

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 is an open-world, paginated, rate-limited read operation, and the description covers discovery, pagination, stop conditions, error signaling, count semantics, and rate limiting. Since an output schema exists, the description need not explain return values. Nothing an agent needs in order to call this tool correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds meaningful semantics beyond the schema. It explains that category IDs 0 and 42 both display as Miscellaneous but identify separate groups, that alpha should be passed as literal # rather than %23 because the server encodes it, and that page restarts when category or alpha changes. These details prevent common misuse of the parameters.

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 first sentence states a specific verb and resource: list GE items within one numeric category. It immediately distinguishes the tool from siblings by naming list_wiki_category_members, lookup_item, and get_item_details and describing their different roles. An agent can identify this as the category-browsing tool without opening any 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?

The description gives explicit routing guidance to alternatives and explains how to discover category IDs and letter filters via get_ge_info. It also states pagination rules: restart page at 1 when category or alpha changes, and stop on empty items because isError signals failure rather than completion. These are concrete when-to-use and how-to-use instructions.

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