list_capabilities

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

No annotations are present, but the description correctly implies a read-only, non-destructive operation. It does not disclose additional behavioral traits like idempotency or authorization requirements, though these are likely not critical for a list 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 description is a single sentence of 6 words with no redundancy or extraneous information. It is optimally concise and front-loaded.

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 tool has no parameters and an output schema exists (per context signals), the description is adequately complete. It does not need to explain return values, but slightly more detail on the nature of the capabilities could 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?

There are no parameters, and schema coverage is 100%. The description adds no parameter information, which is acceptable given zero parameters. Baseline score of 4 is applied per rules for 0-param tools.

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?

Description clearly states 'List supported supervised Data Cloud workflow capabilities' with specific verb and resource, distinguishing it from sibling tools like query and submit operations. However, it does not elaborate on what constitutes a 'capability'.

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 explicit usage guidance is provided. Context implies it should be used before other Data Cloud tools to discover available operations, but alternatives or exclusion conditions are not mentioned.

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