List an Organization's SAML certificates

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds 'certificates registered for SAML SSO validation' but no additional behavioral traits beyond what annotations provide. It does not contradict annotations, but adds little value.

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?

A single, front-loaded sentence with no extraneous words. It efficiently communicates the tool's purpose without redundancy.

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 list tool with one parameter and strong annotations, the description is mostly sufficient. It identifies the resource (SAML certificates) and purpose. A minor gap is lack of output structure description (no output schema), but the tool's simplicity mitigates this.

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%, and the parameter 'saml_id' is well-described with a reference to 'scaleway_iam_get_saml_config's id field'. The tool description adds no further parameter semantics beyond the schema. Baseline 3 is appropriate given high schema coverage.

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 'List certificates registered for SAML SSO validation' clearly states the action (list) and the resource (certificates for SAML SSO). It effectively distinguishes this list operation from sibling tools like scaleway_iam_get_saml_certificate (single certificate) and add/delete variants.

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 guidance on when to use this tool versus alternatives like scaleway_iam_list_api_keys or scaleway_iam_get_saml_certificate. The purpose is implied by the name and sibling context, but the description lacks when-to-use or when-not-to-use instructions.

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