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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the policy context that original game links are the default and agent previews require an explicit quality assessment, which is useful but modest additional disclosure.

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?

It is short, but the middle sentence 'Optional preview quality, pact rules and review' is a fragment that reads as a keyword dump and muddies rather than front-loads the key guidance. Some sentences do not fully earn their place given the ambiguity.

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 read-only guideline resource with no output schema, the description conveys what topics the guidelines cover and when to read them, which is adequate. However, the mixed framing of 'list the original game' versus 'guidelines resource' leaves an agent unsure what is actually returned.

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?

There is a single optional api_key parameter with 100% schema coverage, and the schema itself explains it is unused here. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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 and tool name clearly frame this as reading listing guidelines, but the opening sentence 'List the original game with media and platform links' describes the subject matter of the guidelines rather than the tool's action, which risks confusion with siblings like browse_games or list_my_games. The final clause 'Also resource fanzero://guidelines' only partially rescues the intent.

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?

'Read before submitting' gives a clear triggering condition for the tool, and the closing note about defaults versus agent previews adds context for why an agent should consult it. It does not name any alternative or when-not to use it, so it stops short of a 5.

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