ise_ers_list_authorizationprofile

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says 'Paginated' but provides no detail about what fields are returned, how many results appear per page, whether the response includes total counts, or what happens with large datasets. For a read-only list operation this is somewhat adequate, but the pagination behavior is only vaguely referenced.

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, zero wasted words. Efficient and to the point.

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 no output schema and limited annotations, the description is thin. It tells the agent this lists profiles and is paginated, but doesn't explain return format, ordering, filtering capabilities (if any), or distinctions from other list/search variants. Slightly more detail about what an agent should expect would be valuable.

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 the deployment parameter is documented in the schema but page and size are not. The description mentions 'Paginated' which implies the existence of pagination parameters, but doesn't explain defaults, maximums, or the interaction. This is a minor compensation for the two undocumented 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 'List all Authorization Profiles. Paginated.' states the verb and resource but adds minimal differentiation. There are many sibling list tools (list_profilerprofile, list_guesttype, list_endpointgroup, etc.) that share the identical 'List all X. Paginated.' pattern, so this description does not distinguish it from siblings beyond the resource name in the tool name itself.

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 provides no guidance on when to use this tool vs. alternatives. Siblings include ise_ers_get_authorizationprofile and ise_ers_search_authorizationprofile which target specific profiles or search patterns, but the description doesn't explain the distinction or when listing all is preferred over search/get.

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