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

With no annotations, the description carries the full burden. It conveys that this is a public read of a 'record', which signals read-only access to public data, but says nothing about auth needs despite a token parameter, rate limits, or result size (limit max 50). It discloses the public-read nature but little else.

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?

Extremely dense and front-loaded: the core action leads, followed by a compact scope-by-scope breakdown with zero filler sentences. Every clause maps to a distinct mode.

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 no-annotation, no-output-schema read tool, the scope mapping is useful, but the definition omits guidance on the undocumented limit parameter, auth/token behavior, and how it relates to sibling read tools. Adequate but with clear gaps for a 4-parameter tool.

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 only 50%, and the description compensates well by defining what each scope enum value returns, which the schema leaves as bare enum strings. However, the limit parameter and its 1-50 bound remain undocumented in both schema and description, so it does not fully close the gap.

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 states a clear verb ('Read') and resource ('the public record') and then enumerates four scopes, each with the specific data it returns. It distinguishes its sub-functions well, but does not differentiate itself from overlapping read siblings like recall, activity, or look_around (scope=location's 'recent public events where you are' closely parallels look_around).

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 scope descriptions imply when each mode applies (e.g. scope=game 'a game's log and state'), but there is no explicit guidance on when to choose this tool over recall, activity, or look_around, nor any exclusions. Usage is left to be inferred from the scope list.

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