ise_ers_list_ldap

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

No annotations are provided, so the description carries the behavioral transparency burden. It discloses pagination behavior but doesn't reveal return format, ordering, field selection, or the size limits. For a read-only list operation the risk profile is lower, but with zero annotations the description provides only minimal behavioral context about what the response looks like.

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 concise sentences with front-loaded purpose. The deployment parameter description is embedded richly within the schema rather than cluttering the description. Efficient and minimal waste, though marginally could state the purpose more completely.

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 paginated list tool with no output schema, the description is moderately complete. It covers purpose, pagination, and deployment targeting. However, it lacks guidance on result size expectations, sorting, or how the listing differs from ise_ers_list_ldap's get/search counterparts, and the page/size parameters are left entirely to schema defaults without behavioral context.

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 only 33% - the description covers the deployment parameter in detail (with concrete name/slug/number examples and pointer to ise_list_deployments) but says nothing about page/size semantics beyond the schema's defaults. This partially compensates for the schema gap but not fully, as the page and size parameters lack behavioral guidance in both places.

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?

Clearly states it lists all LDAP Identity Sources with pagination. The verb+resource (list LDAP identity sources) is specific and unambiguous. It distinguishes from get/search_ldap siblings (which retrieve specific items), though it doesn't explicitly contrast with them.

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?

Mentions pagination, indicating it returns paginated results. The deployment parameter documentation is detailed (name/slug/number examples given). However, it doesn't explicitly state when to use this vs the get/search alternatives, and the pagination guidance is minimal without explaining how to navigate pages.

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