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

readOnlyHint already declares it safe, and the description adds a genuinely non-obvious behavior: responses follow the account language, German by default. It also discloses what each entry carries (implementation guidance, XP rewards, affected URLs). It doesn't mention pagination or ordering, but annotations carry the safety profile.

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, no waste, front-loaded with what the resource is, then how to select kind, then the behavioral note about language. 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 no output schema, the description still conveys what comes back (recommendations with guidance and XP; findings with URLs) and the language behavior, which is the main surprise an agent could hit. Nothing needed to call it 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 baseline is 3, but the description adds meaning beyond the schema: it explains what a quest versus an issue actually contains, and that id switches from list to full-detail mode. The schema's description of id ('Id of a single entry for full details') is less informative than the description's framing.

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 the resource precisely: the domain's task list, split into quests (recommendations with XP) and issues (technical findings with URLs). An agent immediately knows it retrieves entries, not mutates them. It doesn't explicitly contrast with nearby siblings like next_actions or complete_quest, which keeps it from 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?

'Use kind=quest or kind=issue; pass an id for full details' is guidance on how to call, not when to choose this tool over alternatives such as next_actions or complete_quest. The usage context (list vs single-entry detail) is implied by the id parameter but never stated as an either/or rule.

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