generate

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

Describes the action (run prompt on GPU tiers) and output (returns completion text). With no annotations, it provides basic transparency but omits details like statelessness, logging, or rate limits.

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?

Two sentences with front-loaded action and return value. Concise and efficient, though adding parameter details could improve without harming conciseness.

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?

With 4 parameters, no annotations, and no output schema, the description is incomplete. It lacks parameter explanations, output format details, and usage context relative to siblings.

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%, so description must explain parameters. Only 'tier' is partially explained with four options; 'prompt', 'system', and 'max_tokens' are not described. Major gaps remain.

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 the tool's function: 'Run a prompt on a GPU model tier' and lists the specific tiers with costs. It distinguishes from sibling tools like 'classify' and 'summarize' by focusing on generative completion.

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 like 'classify' or 'extract'. The description implies usage for text generation but does not help the agent choose among siblings.

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