arcana_find

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

Despite no annotations, description explains algorithm (embed, cosine similarity) and scope, implying a safe read operation. Does not detail rate limits or performance, but sufficient.

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-line summary followed by clean docstring-style parameter list. Every sentence adds value; no wasted words.

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?

Covers core function, parameter meanings, and algorithm. Has output schema which covers return values, so missing output details is acceptable. Lacks edge cases but acceptable.

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 coverage is 0%, but description compensates fully by explaining each parameter: query as natural language, target_uri as optional scope, limit as max results with default.

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 clearly states semantic search using embedding and cosine similarity, but does not explicitly distinguish from sibling arcana_search.

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 optional scope and limit, but no when-to-use or when-not compared to alternatives like arcana_grep or arcana_search.

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