Image server capabilities

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

With no annotations, the description carries the full behavioral burden, and it does so by framing the tool as a reporting/inspection operation ('Report what this image server can do...'). This strongly implies a read-only, non-mutating callaine. It also discloses that results include availability details such as GPU acceleration and security posture, which helps an agent anticipate the nature of the response. It does not mention authorization or cost, but those are unlikely to be concerns for a zero-parameter capability query.

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 with no filler. The first sentence front-loads the tool's purpose and enumerates the specific categories of information, and the second gives a concise usage instruction. Every word earns its place, and the description remains scannable for an agent browsing tool definitions.

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 zero parameters)Skip an output schema, the description is complete: it states what the tool returns, what triggers its use, and why an agent would call it. There is no missing information needed for correct invocation, and the output schema handles return-value details. The description fully covers the contextual needs for this low-complexity tool.

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?

There are zero parameters and the schema coverage is effectively 100% (the properties object is empty), so there is nothing for the description to add about parameter meaning. Per the baseline rule for zero-parameter tools, a 4 is appropriate; the description adds context about what the capabilities report covers, but parameter semantics is trivially satisfied by the empty schema.

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 specific verb ('Report') and resource ('this image server'), then enumerates the exact categories of information returned: supported formats, available operations, resource limits, security posture, and GPU acceleration status. This unambiguously distinguishes the tool from the operation-focused sibling tools, which perform mutations or transformations rather than introspecting server capabilities.

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 gives an explicit usage trigger: 'Call this first when you are unsure which formats or features are available.' This is clear and actionable context for when to use the tool. It does not explicitly state when not to use it or name alternatives, but the zero-parameter introspection role is sufficiently distinct from the sibling image-operation tools that the usage intent is unambiguous.

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