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

Annotations already establish a safe, read-only, idempotent lookup. The description adds useful behavioral detail beyond them, especially that contextual ties affect matching and that `ties` explains how, plus the disambiguation behavior represented by `ask`.

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 front-loaded with the entity definition and includes a dense but useful enumeration of included data, followed by short matching and disambiguation rules. It is somewhat run-on in the first sentence, but most content earns its place for a broad person-profile lookup.

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?

With only two parameters, no output schema, and safe read-only annotations, the description is nearly complete: it explains what data categories the tool returns and how ambiguous matches are handled. It does not specify the exact response shape, but that is a minor gap given the scope described.

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 100%, so the baseline is 3. The description adds meaning to the optional `context` parameter by explaining that supplying a game or studio makes people tied to it win and that `ties` reports the connection.

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 identifies the resource as a developer or RoTerminal member and enumerates the profile, Roblox, studio, group, game, award, post, and job data it covers. It also distinguishes this from general player lookups with 'Never for someone who only plays games,' though it does not use an explicit verb or name sibling alternatives.

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?

It gives concrete usage guidance: pass the named game or studio as context, expect an `ask` response when two people fit, and avoid the tool for someone who only plays games. It lacks explicit named alternatives such as `find` or `search`, so it stops short of a full 5.

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