ise_openapi_repo_list_files

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 does not state whether this is a read-only safety operation (presumably it is, since it's a GET/listing), what the response format is, whether pagination is used, or what happens when the repository doesn't exist. The description merely restates the HTTP endpoint without behavioral detail.

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 a single concise sentence that states the verb, resource, and endpoint. It's appropriately brief with no wasted wording. Slightly more context about the repository concept could help, but the efficiency here is good.

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 moderately simple read/list tool with full schema coverage and no output schema. The description tells the agent what it does but not the behavioral context (read-only nature, return format, error behavior). Given no annotations and no output schema, the description should provide more guidance about what the agent can expect from calling this tool.

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 100%, with 'name' documented as 'Path parameter name' and 'deployment' documented with clear format options and fallback behavior. The description itself adds no parameter detail beyond the endpoint URL, but the schema already does the heavy lifting, so baseline 3 applies.

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 clearly states 'Get list of files in a repository' with a specific verb (list/get) and resource (files in a repository), and specifies the endpoint GET /api/v1/repository/{name}/files. It distinguishes reasonably from sibling ise_openapi_repo_list (list repositories) and ise_openapi_repo_get (get repository), though it doesn't explicitly contrast them. The '[Repository]' prefix adds domain context.

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 explicit when-to-use or when-not-to-use guidance is provided. The description doesn't mention when this tool is preferred over alternatives, nor does it state any prerequisites (e.g., repository must exist). The deployment parameter hints at multi-deployment usage, but no exclusions or context on when to omit it vs. specify it is given.

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