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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the useful detail of what fields are returned, but says nothing about pagination, ordering, or behavior of the limit parameter. With annotations carrying the safety burden, this is an adequate but not rich disclosure.

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?

A single front-loaded sentence listing resource and return payload with no filler. Efficient, though the parenthetical field list makes it slightly dense.

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?

With no output schema, the description helpfully enumerates the returned profile fields and the inclusion of latest opinions, which is a genuine plus. But the limit semantics remain ambiguous and there is no guidance on when to prefer this over overlapping siblings, so it is only minimally complete for a lookup 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 coverage is 50%: influencerId is documented ('id or handle from search') while limit only has type/default/min/max with no description. The description's 'latest opinions' loosely implies limit bounds the opinions returned, but it never states this or clarifies the relationship. It fails to compensate for the undocumented limit parameter.

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 resource (a single influencer) and enumerates the returned profile fields (name, platform, channel, subscribers, opinion counts) plus latest opinions. An agent can tell it retrieves one influencer's details. However, it does not distinguish itself from the siblings influencer_performance or latest_opinions, which overlap conceptually.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as influencer_performance for metrics or latest_opinions for opinion-only reads. The usage is left entirely to inference from the name and sibling list.

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