get_social_media_analytics_audience

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

With no annotations, the description must disclose behavioral traits (e.g., read-only, date range constraints). It only restates the tool's purpose without mentioning any side effects, limitations, or data interpretation details. This is a significant shortfall.

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 sentence that efficiently conveys the tool's core purpose. It is front-loaded and concise, though it could benefit from slightly more substance without adding verbosity.

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 its complexity (3 required parameters, no output schema), the description is incomplete. It does not specify return format, date range inclusiveness, or timezone impact, leaving the agent without crucial operational context.

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 input schema has 100% coverage, so the schema already documents each parameter. The description adds no extra meaning beyond the schema, which meets the baseline but does not improve understanding of parameter usage.

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 'Get audience analytics for a social media account' clearly states the action (get) and resource (audience analytics) and distinguishes it from sibling analytics tools like aggregated, posts, and range. However, it lacks detail on what audience analytics specifically includes (e.g., demographics, engagement).

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?

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives, such as get_social_media_analytics_aggregated or get_social_media_analytics_posts. The agent receives no context for tool selection.

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