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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context by enumerating returned fields (id, name, status, coverUrl) and the status values, which helps interpretation. It does not cover pagination behavior despite limit/offset params.

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 tight sentences, front-loaded with the core purpose, followed by sibling disambiguation, return shape, and downstream usage. No filler.

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?

No output schema, so the description reasonably enumerates returned fields and status values, and routes the agent to consumer tools. It omits pagination guidance for the limit/offset parameters, which is the main remaining gap for a list tool.

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 only 33% — limit and offset are bare integers with no description, and brandId is documented in the schema. The description does not explain pagination semantics or the brandId filter, leaving the limit/offset parameters undocumented in both places.

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 ('List your saved AI influencers') and explicitly distinguishes from the closest sibling, list_characters, by characterizing the influencer as a persistent identity owning a persona, voice, and asset vault. An agent can differentiate without opening schemas.

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?

Provides a clear distinction from list_characters and points to downstream tools (get_influencer, build_influencer_vault, list_influencer_assets) that consume the returned id. However, it does not state when NOT to use this tool or give alternative listing tools (e.g., list_influencer_assets for a different resource type).

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