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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is free to add real behavioral facts: a hard cap of 20 rows, the returned fields (source, retrieval date, context, limits), exact-match semantics for numeric IDs/hashes, and explicit disclaimers that no code is executed and no runtime compatibility is guaranteed. Auth needs and pagination behavior are the only notable omissions.

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?

Four sentences, each carrying distinct information: scope, return shape, matching rule, and the safety disclaimer. Front-loaded with what is readable, with the constraints trailing. Slightly dense but no filler.

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?

There is no output schema, but the description compensates by naming the returned fields and row cap. Combined with annotations covering the safety profile and a small three-parameter schema, an agent has enough to call this correctly; only the default page size and query-length limits are unaddressed.

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 0%, so the description must compensate, and it largely does: the three dataset values are glossed in prose, "at most 20 rows" explains the `limit` maximum, and "numeric IDs/hashes match exact values" clarifies how `query` is matched. It omits the `limit` default of 10 and the query string's length bounds, but the key semantics are recoverable.

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 gives a concrete verb ("Read") and enumerates the three resources it covers (blip sprites, control IDs/default bindings, ped names/hashes), which maps directly onto the `dataset` enum. It does not, however, differentiate itself from the `search` sibling, so an agent must still infer which of the two to pick for a reference query.

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?

Usage is only implied: the tool reads reference data "from the same imported data used on the website." There is no explicit when-to-use statement, no exclusions, and no mention of `search` or `fetch` as alternatives, leaving routing to the agent's inference.

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