get_activity_samples_range

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

With no annotations, the description discloses two key behavioral traits: maximum range of 28 days and that from date cannot be older than 365 days. This goes beyond the schema to help the agent avoid errors.

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: first states purpose, second states constraints. No fluff, front-loaded, every sentence 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?

No output schema, and the description does not explain what activity samples are returned or their format. For a data retrieval tool, more context about return values would improve completeness.

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% with descriptions for from and to. The description adds overall date constraint context but does not elaborate on parameter formats or values beyond what the schema already provides.

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 'Get activity samples for a date range' with specific constraints (28-day max range, 365-day max age). It distinguishes from sibling 'get_activity_samples' by adding the range concept.

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?

Provides constraints on range and date age, which implicitly guide usage, but lacks explicit when-to-use or when-not-to-use compared to sibling tools like 'get_activity_samples'.

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