influencer_profile

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

No annotations are provided, so the description carries some weight. It reveals the data source (the /shop/ store page) which is useful context, but does not disclose typical behaviors like error handling, rate limits, whether non-existent profiles return errors or empty results, or any pagination concerns. For a read-only profile fetch this is moderate but incomplete.

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 a single efficient sentence that communicates the verb, resource, and source URL pattern. It wastes no words. It could arguably include sibling differentiation, but as written it is compact and front-loaded with the core purpose.

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 4 parameters all well-documented in the schema, no output schema, and no annotations, the description does a reasonable job for a relatively simple profile-lookup tool. However, given the large sibling set with several influencer-related tools (influencer_posts, influencer_post_products), it should clarify scope. The output format is unspecified, but for a simple profile fetch this is acceptable.

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 100%, so the schema already documents all 4 parameters fully. The description adds the store page URL pattern showing how influencer_name maps to the URL (e.g., tastemade maps to /shop/tastemade), which is a modest added value beyond the schema. However, it doesn't explain edge cases like spaces or special characters in influencer names.

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 (get), resource (Amazon Influencer profile details), and the source (store page URL example). It distinguishes from sibling influencer tools like influencer_posts and influencer_post_products by focusing on profile-level details, though it doesn't explicitly contrast with them.

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 provides an example URL but offers no explicit guidance on when to use this tool versus influencer_posts, influencer_post_products, or seller_profile. There are no exclusions mentioned. Sibling tools clearly overlap in the influencer domain, so explicit differentiation would be valuable.

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