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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the description needs less safety disclosure. It adds useful behavioral context by stating that checkout and payment actions are not available on this server, which helps an agent avoid inappropriate calls.

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?

One sentence, front-loaded with the core purpose, and no filler. The out-of-scope note earns its place by preventing misuse.

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, read-only, idempotent tool with annotations carrying the safety profile, the description is complete. It identifies the resource type, the public scope, and the key limitation without needing details about parameters or return values.

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 has zero parameters, so the baseline is 4; there are no parameter semantics for the description to clarify. The description correctly stays silent on parameters rather than inventing misleading guidance.

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 title states the verb and resource ('List Evercraft public capabilities'), and the description reinforces it as a 'Read-only public capability catalog.' It is clear enough to identify the tool, though it does not explicitly contrast itself with the sibling tools in the description text.

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 implies this tool is for retrieving the public capability catalog and clarifies that checkout/payment actions are out of scope, which is a mild usage constraint. However, it does not state when to prefer this over get_evercraft_connection_options or match_evercraft_capability.

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