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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety behavior is covered. The description adds useful output-shaping details—prioritization, a maximum of five items, included recommendations, assumptions, and empty sections—but does not add much beyond what the output schema likely covers.

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 two tightly written sentences with no wasted words. It front-loads the main output and then adds secondary items, making it easy to scan.

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 simple read-only tool with rich annotations and an output schema, the description is adequate about returned content and limits. However, it leaves the required 'id' parameter semantically unexplained, which is a notable gap for correct invocation.

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?

The schema has only one required parameter, 'id', with 0% description coverage, and the description never explains what that id identifies or how it should be supplied. The schema establishes that it is a required string, but the description does not compensate for the missing semantic detail.

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 states what the tool returns: the next questions to ask, prioritized, capped at five, with options, recommendation, and rationale, plus assumptions and empty sections. It is specific about content and scope, though it never explicitly distinguishes itself from sibling tools such as grill_answer or grill_brief.

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 provides no explicit guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The phrase 'next questions to ask the person' implies a workflow context, but the description does not tell an agent when to choose this over siblings like grill_answer or grill_get.

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