list_ssl_ssh_profiles

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

With no annotations, the description carries the full burden. It does disclose the ADOM default resolution chain and the exact return keys including error status/message, which is genuinely useful. It says nothing about pagination, result limits, required permissions, or whether the operation is strictly read-only (only implied by 'List').

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 purpose is front-loaded in one sentence, followed by compact domain context and structured Args/Returns blocks. The Returns block partially duplicates the existing output schema, so it is slightly longer than necessary, but nothing is bloated.

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 two-parameter read tool with an output schema, this covers the essentials: both parameters are explained and the return shape is restated. The main remaining gap is behavioral context (permissions, pagination, ADOM lock state) that no annotation supplies.

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 0%, so the description must compensate — and it does, explaining that adom defaults to the DEFAULT_ADOM env var or 'root' and that name_filter is a partial match. Both parameters gain meaning absent from the bare schema, though no format examples are given.

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?

States a specific verb and resource ('List SSL/SSH inspection profiles in an ADOM') and adds domain context explaining what these profiles do. An agent can distinguish it immediately from get_ssl_ssh_profile, create_ssl_ssh_profile, and the other SSL/SSH siblings.

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 listing intent is implied by 'List ... in an ADOM' and the note that profiles are referenced by firewall policies gives useful context. However, there is no explicit guidance on when to use this versus get_ssl_ssh_profile for a single profile, nor any exclusions or prerequisites.

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