acedatacloud_list_apis

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

With no annotations provided, the description carries the burden. It discloses that no token is required and mentions the optional filters, but lacks details on pagination, rate limits, or other behavioral traits such as whether it returns all results or is paginated. The output schema likely covers return format, so this is adequate but not outstanding.

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 sentence followed by a short clarification, front-loaded with the main purpose. Every word is necessary and no filler is present. It is appropriately sized and structured for efficient reading.

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 existence of an output schema, the description need not explain return values. It covers purpose, optional scoping, and authentication requirement. It is mostly complete for a list tool, though it could mention the default limit or ordering, but those are in the schema.

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%, so baseline is 3. The description briefly mentions optional scoping by service and stage, which aligns with parameters, but adds little extra meaning beyond the schema descriptions. It does not elaborate on limit or provide additional context.

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 verb 'List' and resource 'API endpoints', specifies optional scoping by service and stage, and notes what each item carries (path, method, stage, cost). This distinguishes it from sibling list_* tools that list other entities.

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 provides clear context on when to use the tool (listing APIs with optional filters) and mentions 'No token required.' However, it does not explicitly exclude scenarios where alternatives like list_services might be better, though the purpose is sufficiently distinct.

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