search_via_parent

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

The description explains mechanism, blocking behavior, and return values, but annotations set readOnlyHint=false while the tool performs a read-only search. This contradiction lowers the score to 1.

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?

The description is well-structured with front-loaded purpose, mechanism, and parameter details. It is dense but clear, though slightly verbose in the mechanism explanation.

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?

Given the tool's complexity (5 params, no schema coverage, output schema exists), the description covers purpose, mechanism, parameters, and return behavior adequately. It lacks detail on output format but is sufficient.

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?

With 0% schema coverage, the description adds full meaning to all parameters: scope, mode, k, query, timeout_s. It provides defaults, valid values, and bounds (e.g., k=1..100).

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 description clearly states the tool delegates semantic search to the parent process, explaining the mechanism and distinguishing from sibling tools like 'search' or 'dialog_search'. It specifies verb and resource.

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?

Explicitly says to use when child has THREADKEEPER_NO_EMBEDDINGS=1 to avoid loading PyTorch. It implies usage context but does not explicitly state when not to use or compare to alternatives.

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