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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds that this is normative content to be followed rather than data to act on, which is meaningful behavior beyond the annotation. It does not say how large the returned guide is or whether it is a single document or sectioned, which would help an agent budget context.

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?

One dense sentence enumerating coverage plus one imperative sentence on usage; the call-first instruction is placed last where it is most actionable. The topic list is long but each item helps an agent decide relevance, so little is wasted.

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 zero-parameter, read-only guide tool with no output schema, the description supplies both content scope and the mandatory call ordering. The only meaningful gap is the lack of any note on output size or structure, which matters when the instruction is to call it before everything else.

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?

The tool takes zero parameters, so the baseline of 4 applies. The description correctly implies a parameterless full-document fetch, consistent with the empty schema and no enum or nesting concerns.

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 makes clear this returns the reference/rules document for the Gomo Sounds system and enumerates the covered topics (games, folders, entities, events, loops/duration, cost and approval, quality bar, Godot, links/downloads). It is distinguishable from action siblings like create_game or approve_spending, though the verb is implicit ('the full rules') rather than stated as 'returns the guide'.

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?

Explicitly states when to call it: 'Call it FIRST in every conversation, before any other tool, and follow it.' The ordering constraint and the follow-up obligation are both unambiguous, leaving no inference needed about its role relative to siblings.

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