get_social_media_analytics_range

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 repeats the tool's name-like purpose without revealing traits such as authentication needs, rate limits, data aggregation level, or output format. The description adds minimal value beyond the name.

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, efficient sentence that conveys the core purpose without filler. It is front-loaded and easy to parse, though it sacrifices behavioral transparency for brevity.

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 the tool's complexity (5 parameters, large metric enum, no output schema, no annotations), the description is incomplete. It fails to explain return format, pagination, date range limits, or the dependency of metric availability on social network. An agent would lack essential context for correct invocation.

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 description coverage is 100%, so the schema already documents all parameters adequately. The tool description adds no extra meaning about parameters (e.g., clarifying metric availability per network). The baseline of 3 is appropriate as the description neither helps nor harms beyond the schema.

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 time-series analytics for specific metrics' clearly states the verb (Get) and resource (time-series analytics) and distinguishes this tool from siblings like get_social_media_analytics_aggregated or get_social_media_analytics_audience by specifying the time-series nature and ability to select specific metrics.

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 implies usage for time-series data over a date range but provides no explicit guidance on when to choose this tool over siblings, no exclusions, and no context about prerequisites or limitations. The agent is left to infer from the sibling names.

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