ise_ers_list_allowedprotocols

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

No annotations are provided, so the description carries the burden. 'Paginated' is a meaningful behavioral disclosure indicating the tool returns page-based results controlled by page/size parameters. However, it doesn't disclose return format, error behavior, or what fields each protocol record contains. The pagination note is useful but minimal.

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?

Extremely concise at two short phrases, but arguably under-specified. 'List all Allowed Protocols. Paginated.' conveys purpose and the pagination mechanism, but given only 33% schema coverage, the description is too thin to fully compensate for undocumented page/size parameters. It's efficient but sacrifices helpfulness.

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 list/read tool with pagination, the description covers the core behavior. No output schema exists, and the description doesn't explain the return structure. With zero annotations, the description should disclose more about what 'Allowed Protocols' records include. Adequate but leaves the agent guessing about use cases and return format for a simple list utility.

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% (only the deployment parameter has a description; page and size are bare integers with defaults). The description adds 'Paginated' which clarifies page/size purpose, but adds nothing about the format or units of page/size beyond defaults. The deployment parameter has a rich schema description already, so the description adds marginal value there. Partial compensation for the undocumented page/size params.

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 says 'List all Allowed Protocols' with a specific verb (List) and resource (Allowed Protocols). It distinguishes itself from get_allowedprotocols and search_allowedprotocols siblings by the 'List' framing, though it could more strongly differentiate itself. The word 'all' clarifies scope.

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 guidance on when to use this tool vs alternatives. There's a sibling ise_ers_get_allowedprotocols and ise_ers_search_allowedprotocols, but no explanation of when to choose list over get/search. The deployment parameter references calling ise_list_deployments, which is some implicit guidance, but no when/when-not context.

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