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

Annotations already declare readOnlyHint=false, openWorldHint=false and destructiveHint=false, so the description's job is to explain the non-read-only nature — which it does not. The one genuinely additive statement is that OpenAI-originated requests never send COMMIT=true, hinting at a reduced-result mode, but it is phrased ambiguously (a rule? an observation?) and never resolves why a "lookup" is flagged as not read-only.

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?

It is short and front-loaded, with no filler sentences. However, the second sentence is cryptic enough that it does not clearly earn its place — an agent cannot confidently act on "OpenAI requests never send COMMIT=true" without interpretation.

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 no output schema and an unannotated notion of what 'raw JSON' contains, the description should at minimum say what a result looks like or how the offset paging is consumed; it says neither. For a four-parameter query tool with a non-read-only annotation, the definition leaves the agent guessing about side effects and response shape.

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 all four parameters are already documented, establishing a baseline of 3. The description references the commit flag only obliquely via "COMMIT=true" and adds no format, default, or interaction detail (e.g. how commit relates to nextOffset pagination) beyond what the schema states.

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?

"Raw Ask API JSON lookup" essentially restates the tool name and title without saying what the tool actually returns or does — the description never explains that it answers a natural-language query and returns result data. "For app/internal use" adds an audience note but no resource or verb detail beyond the name itself.

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 only routing signal is "for app/internal use," which gives no condition for choosing this over the sibling ask-api or x402-ask-api. There is no statement of when not to use it, no prerequisites, and no mention of cost or credit implications that typically separate these variants.

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