get_config

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The verb 'Get' and the resource 'configuration' imply a non-mutating read, and 'current' conveys that it reflects live state. However, it does not explicitly state that there are no side effects, nor does it describe output shape or error behavior, which would strengthen transparency.

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 efficient sentence with no filler. The core action and object are front-loaded, and the specific contents of the configuration are appended compactly. Every word contributes to understanding.

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 zero-parameter, no-output-schema tool, the description provides sufficient context: it states what is returned (current configuration) and what it includes (loaded model and settings). It could add a note about the exact output format or that calling it has no side effects, but those are not strictly necessary for an agent to invoke such a simple tool 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 input schema declares zero parameters with 100% coverage, so there are no parameter semantics for the description to clarify. The baseline for a zero-parameter tool is 4, and the description appropriately avoids inventing parameter-related details that do not exist.

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 identifies a read operation targeting the current Draw Things configuration and names concrete contents ('loaded model and settings'). It is distinguishable from generate_image and transform_image as those are action-oriented, and from check_status as that targets status rather than configuration. However, it never explicitly contrasts itself with the check_status sibling, so differentiation is implicit rather than direct.

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 check_status, generate_image, or transform_image. No conditions, exclusions, or alternative routing hints are provided. An agent must infer usage purely from the tool name and resource description.

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