acedatacloud_list_usage

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

No annotations are provided, so the description carries the full disclosure burden. It only claims 'complete backend-supported filters,' but does not mention read-only behavior, pagination/ordering semantics beyond schema, authentication needs, or data freshness, making it inadequate for a resource-heavy list operation.

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?

Single sentence, front-loaded with verb and resource. It is short and free of filler; however, the vague 'complete' specifier is somewhat marketing-like and doesn't add concrete detail, but overall the structure is efficient.

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?

The rich input schema (11 self-descriptive params) and presence of an output schema reduce the burden on the description. Yet the one-line description leaves ambiguity about how this tool relates to sibling usage tools and about behavioral details such as pagination limits, so the context is only minimally complete.

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 baseline is 3; all 11 parameters have descriptions, defaults, and constraints. The phrase 'complete backend-supported filters' adds a general guarantee that all listed filters are server-side, but provides no additional syntax or interaction details 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 uses a specific verb ('List') and resource ('API usage'), and adds scope with 'complete backend-supported filters.' This clearly distinguishes from get/export/summary usage tools at a high level, though it does not explicitly name alternatives.

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 states the tool lists API usage with all backend-supported filters, giving clear context for when to use it (filtered list queries). However, it provides no exclusions or alternative recommendations, such as when to prefer acedatacloud_get_usage or usage_summary.

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