metrics_batch

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

Discloses max 50 items, mixed types allowed, order preservation, and response format including error handling. Lacks details on rate limits or authentication, but core behavior is well covered.

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?

Two sentences, front-loaded with purpose, efficient and no wasted words.

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?

Explains return structure despite no output schema, but could detail metrics object fields. Covers error responses. Parameter is well explained, though sibling contrasts are missing.

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?

Description adds max 50 constraint and mixed types beyond schema description ('Public post URLs'). However, schema description contradicts tool description by only mentioning posts. This inconsistency reduces clarity.

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?

Clearly states 'Get metrics for many posts and/or profiles in one call', distinguishing it from singular sibling tools like 'metrics' and 'profile_batch'. Specifies batch capability and return structure.

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?

Implies use for batch operations with 'in one call' and 'max 50', but does not explicitly contrast with singular 'metrics' tool or specify when not to use it. No direct alternative guidance.

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