acedatacloud_get_distribution_trend

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 states 'Get' which implies a read operation, but does not explicitly confirm read-only behavior, mention whether it requires authentication, or describe any side effects. There is no mention of how time bounds are applied or what format the trend buckets take, leaving significant behavioral ambiguity.

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, concise sentence with no wasted words, which is good for conciseness. However, it is under-specified to the point of being terse, lacking essential context that would make the sentence earn its place effectively. It front-loads the purpose but omits necessary elaboration.

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?

Although an output schema exists (reducing the need to describe return values), the description is incomplete overall. It does not explain the meaning of 'trend buckets', the default behavior when time bounds are omitted, or how the output relates to the inputs. The tool has three optional parameters and no documented use cases, making it insufficiently complete for an agent to use confidently.

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 schema covers all three parameters (start_time, end_time, granularity) with descriptions, achieving 100% coverage. The tool description adds no additional meaning beyond the schema, so it meets the baseline for high schema coverage. However, it does not clarify the relationship between time bounds and granularity or provide examples, which could be beneficial.

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 the action (Get) and the resource (caller reward, price, and invitee trend buckets). It is specific enough to convey the tool's core purpose, though it does not differentiate from sibling tools like get_distribution_rank or get_platform_distribution_rank, which also handle distribution 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?

No guidance is provided on when to use this tool versus alternatives. The description lacks any context about prerequisites, scenarios, or exclusions. For example, it does not explain how this trend bucketing differs from rank or platform rank queries, leaving the agent to infer usage.

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