profile_batch

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

No annotations are provided. The description discloses return structure ({ count, results }), order preservation, and error handling (profile object or { url, error }). However, it omits details on idempotency, rate limits, or side effects, which are needed for a batch 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 sentences, front-loaded with the primary action and key constraints. Every word adds value without redundancy.

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 no output schema, the description explains the return format and error behavior. With one well-documented parameter and low complexity, the description covers all necessary information for correct usage.

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 covers the single parameter 'urls' with 100% description, specifying type, max items, and mixed platforms. The description reiterates this without adding new semantic meaning. 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 clearly states the tool retrieves account-level metrics for multiple profile URLs in one call, specifying it is like the 'profile' tool but supports up to 50 URLs. It lists compatible platforms (YouTube, TikTok, etc.), making the purpose unambiguous.

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 contrasts with the sibling 'profile' tool by highlighting batch capability and mixed platforms. It provides a use case (comparing follower counts across creators), but does not explicitly mention when not to use this tool or how it differs from 'metrics_batch'.

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