get_activity_pattern

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

No annotations are provided, so the description carries the behavioral disclosure burden. It clearly reveals that results are aggregated counts, that analytics follow calendar-day granularity, and that hourly granularity is limited to one day. It does not mention timezone handling or limits, but these are minor for this read-style analytics 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 opening sentence immediately conveys the tool's purpose and output shape, and the Args section is compact, parallel, and free of filler. Every line adds meaningful guidance.

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?

All five parameters are semantically covered, the two modes are fully described, and the output schema handles return-value details. An agent has enough information to select and invoke the tool correctly without additional lookup.

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 0%, so the description must compensate, and it does thoroughly. It defines each granularity value, explains which arguments apply to which mode, states that species is required for hourly but optional for daily, and gives the YYYY-MM-DD date format.

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 states a specific operation and resource: temporal detection activity, returning counts per day over a date range or per hour for one day. This clearly distinguishes it from sibling tools that return individual detections or species summaries, even though no sibling is named.

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?

It gives clear usage context by explaining the two granularity modes and their constraints, such as hourly data being available for a single day only and requiring date and species. It does not explicitly cite alternative tools, but the nature of the output makes the appropriate scenario obvious.

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