get_results

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

Adds value beyond annotations by revealing that table_metadata.json is automatically embedded, avoiding separate HTTP fetches. Also outlines key response fields. Annotations already indicate readOnlyHint=true, so the description complements without contradiction.

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?

Well-structured with a clear opening sentence, bullet points for key response fields, and a 'START HERE' emphasis. Every sentence is informative and earns its place; no fluff.

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 tool with one parameter, high schema coverage, and an output schema, the description is comprehensive: explains purpose, parameter usage, and response structure. Provides a mental map of the output without redundancy.

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%, baseline is 3. Description adds clarifying detail that job_id and session_id are the same string, and implies job_id must be for a completed job, which goes beyond the schema's description.

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?

Description clearly states 'Fetch the final validated/enriched results for a completed job,' providing a specific verb, resource, and constraint. It distinguishes from sibling tools like get_job_status or get_preview_state by focusing on completed job results.

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?

Provides context that job_id equals session_id and emphasizes starting with results.markdown_table. However, it does not explicitly state when to use this tool versus alternatives (e.g., get_job_status, get_preview_state), lacking exclusions or when-not scenarios.

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