Show Config

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds minimal contextual scope by saying 'selected profile configuration' and does not contradict the annotations, but it does not disclose additional behavioral traits such as default resolution behavior or error handling.

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 sentence with no filler, and the core action and object are front-loaded. It is concise without being a tautology.

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 read-only tool with full parameter documentation, zero required parameters, and an output schema, the description is mostly sufficient for invoking the tool correctly. The main gap is the unresolved relationship with config_get and config_profiles, which affects tool selection more than invocation.

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?

The input schema provides complete descriptions for all three parameters (100% coverage), so the description does not need to repeat parameter details. The description's mention of 'selected' adds little beyond what the 'profile' parameter documentation already conveys.

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 a specific action ('Return') and a concrete resource ('the selected Cloudeval CLI profile configuration'), so it clearly indicates what the tool does. However, it does not distinguish itself from the sibling tools config_get and config_profiles, which could plausibly overlap with 'show config'.

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?

There is no guidance on when to use this tool versus alternatives like config_get or config_profiles. The word 'selected' implies a profile is already chosen, but the description does not explain what 'selected' means or when this tool should be preferred over its siblings.

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