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

The description discloses that the tool costs 1 credit and requires an API key, which are important behavioral traits not visible in the schema or annotations. However, it doesn't mention what happens on failure (e.g., insufficient credits, invalid key), rate limits, or whether the operation is read-only or mutating. With no annotations provided, the description carries the burden but only partially fulfills it.

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 two short sentences, front-loading the core action and then adding cost and auth requirements. Every sentence earns its place, though it could be slightly more structured by separating the cost/auth info from the main action.

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 3 parameters, no output schema, and no annotations, the description is too thin. It doesn't explain the model parameter, the expected prompt format, the output structure, or error handling. The cost and API key info is useful but incomplete for an agent to confidently invoke the tool correctly.

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 description coverage is 0%, so the description must compensate for the lack of parameter documentation. The description mentions 'API key' and 'costs 1 credit' but doesn't explain the 'model' parameter's allowed values or the 'prompt' parameter's format/length constraints. The default model 'qwen3.8fast' is in the schema but not explained in the description, leaving the agent to guess what models are available.

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 states a specific verb ('Run LLM inference') and a resource ('RTX 4080'), which clearly identifies the tool's core function. It doesn't explicitly differentiate from siblings, but the sibling names (titan_beacon, titan_collect_key, titan_credits, titan_order) suggest different purposes, so the main action is clear enough.

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?

The description implies usage context by mentioning cost and API key requirement, which signals when this tool is appropriate (when the user wants LLM inference and has credits/key). However, it doesn't explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites beyond the API key.

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