instant_headshot_run_headshot_generation

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

With no annotations, the description carries full burden. It discloses processing time estimates and content moderation but omits details on error handling, quota limits, or output format.

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?

Three sentences, front-loaded with the primary action, no extraneous text. Efficiently lists key features 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?

Covers inputs and moderation but lacks output schema or detailed behavior (e.g., how custom_prompt interacts, what moderation failure entails). Adequate for basic use but incomplete for nuanced scenarios.

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 56%. The description adds value by explaining time estimates for quality and hinting at output variable usage, but many parameters (e.g., style, background) rely solely on enums without further context.

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 verb 'generates' and the resource 'AI professional headshots' using a specific model. It lists key configurable options, making it easy to distinguish from the sibling tool 'instant_headshot_render_headshot_report'.

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 for generating headshots but lacks explicit guidance on when to choose this tool over alternatives (e.g., the render report tool) or prerequisites like reference photo requirements.

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