sdcloud_list_content_security_profiles

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

No annotations are provided. Description mentions 'optional pagination, filtering, and sorting' but does not explain behavior such as how pagination works (e.g., size=0 returns max results), sortby syntax, or filter format. The count parameter behavior is only in schema. Description adds minimal behavioral context beyond the schema.

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?

Single sentence, no redundant information. However, it could be slightly expanded to note output structure or count parameter effect without losing conciseness.

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 no output schema, the description should provide more context about the return value (e.g., list of profile objects with details). It does not mention that count=true returns only a count, which is a significant behavior. For a list tool with 5 parameters, the description is too sparse.

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 100%, so the schema already documents all 5 parameters with descriptions. The description only summarizes with 'with optional pagination, filtering, and sorting', which does not add significant new meaning. Baseline 3 is appropriate.

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 content security profile objects' with a specific verb and resource. It mentions optional pagination, filtering, sorting, which distinguishes it from get, create, update, delete siblings, but does not explicitly contrast with other list tools for different profile types.

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 implies usage: use when you need to list multiple profiles with optional parameters. However, it provides no explicit guidance on when to use this tool vs alternatives (e.g., get for single profile, or other list tools for different resources).

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