ise_openapi_repo_get

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. The description only mentions the HTTP method (GET) and endpoint, but says nothing about what the returned data contains, error behavior for non-existent repos, permissions/authentication requirements, or whether the 'deployment' parameter affects behavior. This is a read operation but that's not even explicitly stated beyond the GET verb.

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?

Single concise sentence in the description is efficient. The deployment parameter's schema description is detailed but appropriate. No fluff or redundancy. The '[Repository]' prefix adds organizational context.

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 GET-by-name tool with two parameters and 100% schema coverage, this is reasonably complete. The schema's deployment parameter guidance is thorough. However, without annotations or an output schema, the description could add more value by mentioning what data is returned. Given the tool's simplicity, it's borderline adequate but could benefit from noting error/not-found behavior.

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%, so the schema already documents both parameters. The description's name parameter ('Path parameter name') and deployment parameter (with detailed guidance referencing ise_list_deployments) are actually quite helpful. The 'deployment' parameter description in the schema is rich and well-written, covering how to specify a deployment and pointing to a sibling tool for choices.

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 states 'Get a specific repository' with a clear verb (Get), resource (repository), and the HTTP endpoint. It distinguishes from sibling ise_openapi_repo_list (which would list all) by using 'specific'. However, it doesn't clarify what a 'repository' is in the ISE context or what distinguishes it from the many other Get* tools.

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 purpose is clearly a single-item retrieval by name, which is implied by the tool name and 'Get a specific'. However, no explicit when-to-use vs alternatives guidance is given, and no mention of when to use list vs get. The sibling ise_openapi_repo_list provides an implicit alternative but no explicit direction.

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