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

Annotations declare it is not read-only and not destructive, so the bar is lower. The description adds crucial context beyond annotations: it is free, plan-gated with specific limits (starter 1, pro 5, enterprise 10, free 0), returns the new influencer id, and cannot be idempotent as each call creates a new profile. This is rich transparency.

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 dense but well-structured, front-loading the core purpose and cost. It uses multiple sentences efficiently, though the second sentence about attach_influencer_reference is slightly tangential to the creation act and could be separated as a note.

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 7 parameters with 86% schema coverage, no output schema, and annotations covering mutability, the description completes the picture by stating cost, plan limits, return value, and next-step workflow. An agent has everything needed to invoke correctly and plan subsequent calls.

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 high at 86%, so the baseline is 3. The description implies the required 'name' parameter but adds no syntax or format details beyond what the schema provides. It does clarify the return value (influencer id) but that is not parameter semantics.

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?

States a specific verb+resource ('Create a new persistent AI influencer identity') and maps it to the dashboard equivalent. It clearly distinguishes itself from siblings like generate_influencer_look and build_influencer_vault by noting those are the credit-spending steps.

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?

Explicitly states when to use this tool ('FREE — this just creates the profile row') and names the alternative steps when the user wants the look or vault. It also provides a clear conditional workflow: 'To start from the user's own photo, call attach_influencer_reference next'.

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