mimry_find

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

With no annotations, the description carries the full behavioral burden. It discloses that snippets are 'bounded' and gives the offset=0 pagination contract, but says nothing about read-only nature, what the semantic flag changes, or how the many snippet-size limits interact.

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 the core function front-loaded and no filler. But for a 13-parameter tool the treatment is under-sized rather than genuinely concise, and 'Pass offset=0 on page one' is vaguely worded.

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?

An output schema exists, so return values needn't be described. Still, a 13-param tool with no annotations and 0% schema coverage leaves the majority of inputs undocumented, so the definition is not complete enough for confident invocation.

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?

13 parameters at 0% schema description coverage, so the schema provides only names, types, and defaults. The description touches only 'snippets' and 'offset', leaving semantic, root, languages, path_globs, exclude_globs, and all snippet-size params unexplained in both the schema and the text.

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+resource ('Search files') and hints at the snippet capability via 'bounded live-source snippets'. However, it never distinguishes itself from siblings like mimry_symbol or mimry_path, so an agent cannot tell which search tool to pick from the text alone.

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 only instruction is 'Pass offset=0 on page one', which is a pagination mechanic, not routing guidance. There is no indication of when to prefer this over mimry_symbol, mimry_path, or mimry_related, so the agent gets no help choosing among siblings.

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