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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the description's safety profile is well covered. The description adds a meaningful constraint: the caller needs a 'game-only handle', not a general session handle. It could still explain more about what happens with an invalid/expired handle, but it is not materially misleading.

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 one compact sentence that front-loads the action and the target resource. There is no redundant phrasing, and the caveat about the game-only handle appears naturally at the end without wasting tokens.

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?

This is a simple read-only tool with a single parameter, full schema coverage, and an output schema, so the description does not need to document return values. The main missing piece is why not use a similar sibling tool, but that gap is already captured in the Usage Guidelines dimension.

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% and the single required parameter, sessionHandle, is already described as a '30-day game-only session handle.' The description's 'using a game-only handle' reinforces that semantics but does not add meaningful new meaning beyond the schema.

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 clearly states a verb and resource: 'Read queue, match, and weekly-list status' and ties it to a specific input type ('using a game-only handle'). The title further clarifies the domain ('my SWARM SYNC status'). However, it does not explicitly differentiate from sibling read tools such as get_arcade_match or get_agent_entry_status, so it stops short of fully standing apart.

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 this is for reading status with a game-only handle, but gives no explicit when-to-use guidance, prerequisites, or exclusions. It does not name any alternative sibling tool or explain when an agent should pick this over similar status-readers. An agent must infer the intended use case from the title and schema.

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