get_repository

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

No annotations are provided, so the description must bear the full burden of behavioral disclosure. It states that the tool is a read operation ('Get') and returns a JSON string, but it does not mention side effects, performance characteristics, or any required permissions. For a simple get tool, this is incomplete.

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 extremely concise, using only a few lines (title, args, returns). Every sentence serves a purpose, and there is no redundant information. It is front-loaded with the core action.

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?

Given that an output schema exists, the description does not need to detail return values. It provides an adequate summary of what is returned (repository details including connection status and type). Minor omissions like error handling or prerequisites are negligible for a straightforward get 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?

With 0% schema description coverage, the description adds significant value by explaining each parameter: 'connection_name: Name of the Argo CD connection' and 'repo: Repository URL (e.g., ...)'. This provides context and examples beyond the bare input schema.

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 the tool's function: 'Get detailed information about a specific repository.' This is a specific verb+resource combination that distinguishes it from sibling tools like list_repositories (which lists repositories) and get_cluster (which retrieves cluster details).

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?

Usage is implied: use when you need details on a specific repository. However, there is no explicit guidance on when to use this tool versus alternatives like list_repositories, nor any prerequisites or conditions. The description lacks explicit when-not scenarios.

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