analyze_results

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

No annotations provided, and description does not disclose whether this tool is read-only, destructive, or requires special permissions. The existence of an output schema is not leveraged to clarify return structure or side effects.

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?

Description is a single sentence with no extraneous words, making it concise. However, it lacks structure (e.g., separate sections for purpose, usage, parameters) that could improve scannability.

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?

Despite having an output schema, the description does not mention return values or pagination. Important context about when and how to use the tool is missing, especially given the absence of annotations.

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 sole parameter job_id has no description in the input schema, and the tool description does not explain its meaning or how to obtain it. Schema coverage is 0%, so the description fails to add semantic value.

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 the tool detects outliers (Z-score > 3) and trends in query results, with a specific verb and resource. It distinguishes from siblings like execute_query or get_job_results_summary by focusing on analysis rather than execution or retrieval.

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?

No guidance on when to use this tool versus alternatives. Does not mention prerequisites like a prior query execution, nor does it suggest scenarios where sibling tools (e.g., get_job_results_summary) might be more appropriate.

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