social_get_influencer

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only indicates a read operation ('Get detailed information') but does not note any potential side effects, rate limits, data freshness, or behavior when the handle is invalid or not found.

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, front-loaded sentence without redundancy. It is appropriately sized for a tool with one parameter, though it is slightly terse and could be expanded without losing conciseness.

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?

The tool is simple with one well-documented parameter, but there is no output schema and the description does not clarify what 'detailed information' includes (e.g., profile, metrics, posts). This is a minimal but adequate description for a basic lookup, though additional context would improve completeness.

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?

The schema description coverage is 100% (handle is described as 'Twitter/X handle of the influencer'), so the baseline is 3. The description adds minimal extra meaning beyond the schema, only reinforcing that the handle refers to a specific influencer.

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 uses a specific verb ('Get') and resource ('detailed information about a specific influencer'), clearly distinguishing it from sibling tools like social_get_influencers (plural) and social_get_influencer_posts. The parameter handle further clarifies the target.

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 no guidance on when to use this tool versus alternatives. Sibling tools such as social_get_influencers and social_get_influencer_posts exist, but the description does not mention them or any context for choosing this tool.

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