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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. 'Read-only and non-transactional' largely restates those hints, while 'public-safe' adds a small amount of context about what content is exposed. No disclosure of pagination or result size beyond the schema's limit parameter.

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?

Two short sentences with zero padding and the purpose front-loaded. The second sentence is partly redundant with the annotations, which slightly dilutes the value density but does not harm readability.

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-required-parameter read tool with no output schema and full annotation coverage, the description supplies enough to call it correctly. It lacks any hint about what the returned directory looks like or how results are scoped, but with annotations carrying safety and the schema carrying parameters, no critical gap remains.

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?

Schema description coverage is 100%, and the single 'limit' parameter is fully documented in the schema with default, min, and max. The description adds no syntax, format, or interpretation beyond what the schema already provides, so the baseline 3 applies.

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?

States a specific verb ('Return') and resource ('current public-safe Evercraft capability directory'), and 'public-safe' adds a meaningful scope qualifier. However, it does not distinguish itself from siblings like match_evercraft_capability or get_evercraft_connection_options, leaving the agent to infer that this is the unfiltered enumeration tool.

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 explicit statement of when to use this tool versus the sibling match/get tools. The only implicit signal is the generic verb 'list', which suggests enumeration, but neither prerequisites nor exclusions are provided.

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