ra_api_raw

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that it returns raw JSON and acts as an escape hatch, but it does not disclose output truncation via max_chars, rate limits, or error behavior.

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?

Two tightly written sentences with the core role front-loaded and no wasted words. The fallback guidance follows immediately and the example is embedded efficiently.

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 an open-world escape-hatch tool with no output schema, the description should clarify return format and truncation behavior. 'Raw JSON' is a start, but max_chars output limiting and any invocation constraints remain undocumented, leaving meaningful gaps.

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 67%, with max_chars having no description anywhere. The description only illustrates the endpoint parameter with 'GetGameExtended' and adds no meaning for the params object or max_chars behavior, so it does not compensate for the schema 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?

States the resource ('raw JSON from any RA Web API endpoint') and gives a concrete example endpoint. The 'escape hatch' framing plus 'Prefer the dedicated tools' distinguishes it from the many specific sibling tools, though it never uses an explicit verb like 'fetch' or 'call'.

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?

Clearly positions itself as a fallback by saying 'Prefer the dedicated tools,' which tells the agent to use siblings when available. It stops short of naming the exact condition or listing the relevant dedicated alternatives explicitly.

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