get_infrastructure_config

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

No annotations exist, so the description must fully disclose behavior. It only states the API endpoint (config.openshift.io/v1) but omits any side effects, authentication needs, or output structure. The existence of an output schema partially mitigates, but the description itself adds minimal behavioral context.

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 short sentence, which is concise but lacks substantive information. Every word earns its place, but more content is needed for completeness within the compact structure.

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 the tool's low complexity (one optional parameter) and the presence of an output schema, the description is incomplete. It fails to explain the typical use case, relationship to sibling tools, or any constraints, leaving the agent with limited actionable 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 description coverage is 0%. The single parameter 'cluster' has no description in the schema or the tool definition, leaving its purpose and acceptable values unclear. The parameter name hints at a cluster reference but lacks explicit documentation.

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 retrieves Infrastructure and Network configuration CRDs from config.openshift.io/v1, specifying both the resource type and API source. However, it does not explicitly differentiate from sibling tools like 'get_resource', though the specific CRD focus provides some distinction.

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 guidance is provided on when to use this tool versus alternatives such as 'get_resource' or 'get_cluster_info'. The description does not mention prerequisites, limitations, or context for use.

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