crystal_search

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

No annotations are provided, so the description carries the full burden. It discloses the default no-filter behavior and sort order, which is genuinely helpful, but says nothing about read-only nature, permissions, result format, or pagination limits beyond what the schema already states.

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 sentences, front-loaded with the verb and resource, with the default-behavior caveat placed second. Dense but efficient; the parenthetical enumeration is long yet earns its place by signaling breadth.

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 15-parameter read tool with no annotations and no output schema, the description covers defaults and filtering scope but omits return-value shape and result-set behavior. Adequate but leaves gaps the schema alone can't fill.

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%, so every parameter is already documented in the schema. The description lists filter categories that map onto those parameters but adds no syntax, defaults, or semantics beyond the schema, making the baseline 3 correct.

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 ('Search and list') and resource ('crystals'), and enumerates the filter dimensions it supports. An agent can distinguish this from crystal_stats or crystal_triage, though it doesn't explicitly name those siblings as alternatives.

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?

Gives one useful context cue: called with no filters it lists active crystals, most recently active first. But it offers no when-to-use vs. alternatives guidance (e.g., when to reach for crystal_stats or crystal_hydrate instead), leaving usage largely implied.

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