Show GPT-image config

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

With no annotations, the description bears responsibility for behavioral disclosure. It usefully reveals that the API key is masked, and the verb 'Show' implies a read-only operation. However, it does not mention potential errors (e.g., missing config file) or other side effects, though for a simple getter this is minor.

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 two sentences, front-loaded with the main purpose and immediately listing the returned fields. The second sentence adds the masking detail and a pointer to set_config, with no wasted words.

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 parameterless getter with an output schema present, the description fully covers what the tool does and what it returns. It names all output fields and notes masking, which is sufficient context for an agent to invoke it correctly.

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 tool has zero parameters, so the schema provides no param details and the description doesn't need to explain any. The baseline for 0 parameters is 4, which is appropriate; no additional param semantics are required.

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?

Description states a specific action ('Show') on a specific resource ('the current GPT-image configuration') and enumerates the exact fields returned. It clearly distinguishes from the sibling set_config by indicating this tool displays rather than modifies.

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 description explicitly tells when to use this tool (to view configuration) and provides an alternative: 'Use set_config to change any of these values.' This effectively explains when not to use it for modifications.

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