get_prediction

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

Discloses behavior for two completion scenarios (ad-hoc and batch) with specific returned fields, including that curl_command is tokenized for safety. However, does not cover pending or failed states.

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?

Concise, with front-loaded purpose and bullet points for scenarios. Minor room for improvement in structuring edge cases.

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?

Adequately covers main completion states but lacks description for pending, failed, or invalid prediction_id. Output schema exists, reducing need to describe return values.

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 only parameter, prediction_id, has no description in the schema (0% coverage) and the description adds no semantics beyond 'by prediction id', missing format, constraints, or examples.

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 'Fetch prediction status and result by prediction id.' with a specific verb and resource, distinguishing it from siblings like run_prediction or list_predictions.

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 explicit guidance on when to use this tool versus alternatives. It does not mention criteria for choosing get_prediction over run_prediction, list_predictions, or other related tools.

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