gamma_get_status

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

No annotations are provided, so the description bears full burden. It covers polling behavior and output fields but omits error handling, timeouts, or consequences of invalid generation_id. This leaves gaps for an agent to anticipate failure modes.

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 compact and logically ordered: purpose, preconditions, polling behavior, output fields, and an explicit Args section. Every sentence adds value without redundancy.

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?

Given the tool's simplicity (1 parameter, output schema present), the description covers all necessary aspects: what it does, when to use it, how to use it, and what results to expect. No critical gaps remain.

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 0%, but the description explicitly states the single parameter generation_id is 'The generationId returned from a generate call,' providing clear provenance. No additional constraints are needed for a simple ID string.

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 'Poll a generation job to retrieve status and results,' specifying a specific verb and resource. It distinguishes itself from sibling tools like gamma_generate and gamma_describe_options by focusing on status retrieval after generation.

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?

Explicitly instructs to call after gamma_generate or gamma_generate_from_template with the returned generationId. Provides polling frequency guidance and expected terminal statuses ('completed' or 'failed').

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