list_analysis_profiles

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

No annotations are provided, so the description carries the burden. 'List all' strongly implies a read-only, unfiltered retrieval, which is a basic behavioral statement for a zero-parameter operation. However, it does not disclose response shape, pagination, ordering, or potential rate-limit behavior.

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?

One short, front-loaded sentence with no filler. 'For media processing' adds useful domain scope without bloating the description.

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?

For a simple parameterless list tool, the description is nearly complete: an agent knows what it lists and that no arguments are required. It omits return-value details and does not route users to get_analysis_profile for single-profile details, but the low complexity makes those omissions minor.

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 tool has zero parameters, so there is no parameter semantics gap. The schema is trivially complete, and the baseline for 0-parameter tools is 4. The description does not need to add parameter-level detail.

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 a specific resource ('analysis profiles'), and the word 'all' distinguishes it from the singular get_analysis_profile sibling. It clearly conveys a read-only listing operation.

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?

There is no guidance about when to use this tool instead of get_analysis_profile or other list_* tools. No alternatives, exclusions, or typical use cases are mentioned; the only implied context is that you list all profiles when you want an overview.

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