ise_ers_list_profilerprofile

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

No annotations are provided, so the description carries full burden. The description only discloses pagination behavior but does not state whether this is a read-only operation, what the default page/size behavior entails, whether it returns all fields of profiles or summary data, or any rate limits. For a list operation with zero annotation coverage, it should disclose more behavioral detail about return format and defaults.

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?

Two short sentences with zero waste. 'List all Profiler Profiles. Paginated.' is efficient and front-loaded. However, it might be too sparse given the missing parameter context and absence of annotations, but for conciseness alone it scores well.

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?

This is a paginated list tool with no output schema, no annotations, and low parameter coverage. It provides the essential purpose but lacks behavioral disclosure about return format, defaults, or what fields are returned. Given sibling tools like ise_dc_view_profiled_endpoints_summary exist and the naming parity with dozens of other list tools, a richer description would help distinguish behavior. The description meets the minimum but leaves gaps.

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 only 33%, meaning 2 of 3 parameters (page, size) lack descriptions in the schema. The description adds no parameter-level detail beyond 'Paginated', so page and size semantics are implicit only. The deployment parameter does have a schema description with helpful examples and guidance. The description itself adds marginal value over the schema for parameters.

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 states 'List all Profiler Profiles. Paginated.' which clearly identifies the verb (list) and resource (Profiler Profiles) with a scope note about pagination. It distinguishes from sibling tools like ise_ers_get_profilerprofile (single fetch) and ise_ers_search_profilerprofile (search against criteria), though it does not explicitly name these alternatives. The purpose is clear and specific.

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 'Paginated' note implies the tool returns pageable results, giving some usage context. The description does not explicitly state when to use this versus ise_ers_search_profilerprofile or ise_ers_get_profilerprofile. However, the naming convention across siblings (list vs search vs get) is consistent and inferable. No explicit exclusions or alternative guidance is given.

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