ise_openapi_repo_list

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

No annotations are provided, so the description carries the full burden. It fails to disclose this is a read-only list operation, whether pagination behavior is relevant, what the response format is, whether it requires any auth/role, or how many repositories one might expect. The page/size parameters imply pagination but the description doesn't state any behavior about it. For a read tool with zero annotation coverage, this is a significant transparency gap.

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?

The description is compact and to the point. The '[Repository]' prefix helps categorize the tool. However, it front-loads minimal information and the endpoint mention is somewhat redundant given the pattern of OpenAPI-derived descriptions. It could use the space more effectively to describe what a repository is and what the list returns.

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?

With no output schema and no annotations, the description could explain what the returned list contains. The tool is relatively simple (list operation with pagination), so the baseline need is lower, but the description leaves the reader unclear about what repositories are (backup repos?), the shape of the response, and how page/size interact. Adequate for a simple list tool but could be more complete.

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% (only 'deployment' has a description). The description compensates well for the two undocumented parameters (page, size) through their defaults in the schema, and adds genuinely helpful semantics for the 'deployment' parameter explaining format options (name, slug, or number) and default behavior. Given the low schema coverage, this is reasonably good compensation.

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 identifies the resource as repositories list from the ISE deployment repository ([Repository] Get list of repositories) and mentions the GET endpoint. However, it's quite generic and doesn't clarify that this relates to backup repositories specifically (as evidenced by sibling tools like ise_openapi_repo_create/update/delete and backup tools). It doesn't distinguish well from other list operations in the sibling set, and the meaning of 'repository' in the ISE context is left ambiguous.

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 'deployment' parameter description offers solid guidance on when to use it: 'Omit to use the only/default deployment. Call ise_list_deployments to see the choices.' However, there's no general guidance on when to use this tool vs other list tools, no stated use cases, and no exclusions or alternatives for listing repositories. The endpoint reference provides partial context but no strategic usage guidance.

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