gimp_status

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

Description implies a non-mutating check/return operation by using 'check', but with no annotations it does not explicitly disclose side effects, error handling, or permissions. Acceptable for a status tool but minimal.

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?

Single sentence, front-loaded with action, no filler.

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 status tool with output schema, the description captures the essential function, but lacks context on typical usage scenarios (e.g., pre-flight check before GIMP operations).

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?

Tool has zero parameters, so schema provides complete coverage; description need not add parameter semantics.

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 uses specific verb 'check' with resource 'configured GIMP connection' and specifies output as 'basic session status'. It is clear but does not explicitly distinguish from sibling gimp_capabilities, though the function is evidently a status/health check.

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 on when to use vs alternatives or prerequisites. Only states what it does, not when to invoke it.

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