businessinsider_author

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

No annotations are present, so the description carries full behavioral disclosure. It discloses that the tool returns a public profile (implying read-only) and lists the returned data, but it does not describe behavior on missing/invalid identifiers, potential errors, or any side effects. This is adequate but minimal for a lookup tool.

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 two compact sentences. The first sentence front-loads the action and resource; the second lists the payload. No filler or redundant phrasing; every word earns its place.

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?

Since there is no output schema, the description usefully explains the return payload. However, it does not clarify input requirements (e.g., that at least one of url/slug is expected) or error behavior when the author does not exist. This leaves minor ambiguity, though the schema partially covers parameter roles.

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 100%: both 'url' and 'slug' have descriptive text, with 'url' explicitly noted as an alternative to 'slug.' The tool description adds no parameter-level meaning beyond what the schema already provides, so baseline 3 applies.

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 starts with a specific verb and resource: 'Get a Business Insider author profile.' It enumerates the exact return fields (name, job title, bio, social accounts, recent articles) and explicitly says 'one' author, making it distinct from sibling author tools for other publications and from Business Insider article/headline tools.

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 purpose clearly implies usage when a Business Insider author profile is needed, but the description provides no explicit when-to-use/when-not-to-use guidance or references to alternatives. It does not mention that at least one of url or slug should be provided, nor does it differentiate from other *_author tools beyond the 'Business Insider' qualifier.

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