generate_font_pro

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

No annotations are provided, so the description carries the full burden. It discloses the async nature (returns job_id) and the need for polling, but does not mention potential failures, rate limits, or cost implications beyond what is hinted in the image_size parameter description.

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 sentences with no fluff. It front-loads the purpose and immediately provides the key behavioral information (async, polling). Every word adds value.

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 no output schema, the description sufficiently describes the outputs (glyph atlas + .ttf). It could mention how to use the result or what the job status returns, but the polling tool (get_job_status) is a sibling. The description is adequate for an agent to understand the workflow.

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 100%, so the baseline is 3. The description does not add new meaning to individual parameters; it only restates the main input 'description'. It does not explain parameters like seed, weight, or glyph_px beyond what the schema provides.

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 explicitly states the action (generate font), the input (text description), and the outputs (glyph atlas and .ttf font). It clearly distinguishes from sibling tools as it's the only font generation tool.

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 tells the agent to poll get_job_status for the result, providing a clear next step. However, it does not specify when not to use this tool or contrast with other generation tools, though no sibling font tools exist.

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