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

Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds behavioral context beyond annotations: 'newest first' and 'grouped by moderation task.' It also reinforces read-only, consistent with annotations. No contradiction, and no critical behavior (e.g., authentication, pagination) is disclosed, but the added ordering/grouping is valuable.

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 a single front-loaded sentence that captures purpose, ordering, grouping, and read-only nature without redundant words. It earns its place for a simple read tool.

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?

For a one-parameter, read-only tool with strong annotations, the description is sufficient. It specifies scope ('on a game') and output organization ('newest first, grouped by moderation task'). No output schema exists, but the description gives enough context for a correct call. Minor omission: it doesn't describe the returned data structure, but that is acceptable given simplicity.

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 100%; the only parameter, applicationId, is already documented as 'Application (game) id, as returned by list_applications.' The tool description adds no parameter-level detail beyond mentioning 'on a game.' Baseline 3 applies because the schema fully covers the parameter.

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 title 'Read the moderation correspondence' and description 'The moderation correspondence on a game, newest first, grouped by moderation task. Read-only.' clearly identify a specific verb (read/list), resource (moderation correspondence on a game), and key behaviors. No sibling tool appears to handle moderation correspondence, so it is easily distinguished.

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 implies usage (when you need to view moderation correspondence for a game) but does not explicitly state when to use it or when not to, nor does it name alternatives. Since there are no sibling moderation tools, ambiguity is low, but explicit guidance is absent.

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