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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that this is a full-text search, which implies a read-only operation, but it does not mention match semantics, pagination behavior, limit handling, faceting behavior, or what the response contains. This is significantly under-disclosed for a tool with seven parameters.

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 a single sentence with no wasted words and front-loads the action. It is appropriately terse, though it may be too sparse for the tool's complexity; that issue is more relevant to contextual completeness than conciseness.

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 search tool with seven optional filtering parameters, no annotations, and many sibling tools, this one-sentence description is incomplete. It does not explain what facets, min_quality, section, or agent do, nor does it provide enough context for an agent to decide when this tool is the right choice. The presence of an output schema helps understand return shape, but critical selection and parameter semantics are missing.

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?

The input schema has no parameter descriptions, and the description does not compensate. 'Full-text search' gives some meaning to the required query parameter, but optional parameters like facets, min_quality, section, and agent are left entirely unexplained. With 0% schema description coverage, the description needed to clarify these but does not.

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 names a clear action (full-text search) and a specific resource (security-recipes documents), so it is not a tautology and tells an agent what the tool operates on. However, it does not explicitly differentiate it from sibling tools like recipes_get, recipes_list, or recipes_cve_search, so it is clear but not sharply distinguished.

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 description gives no guidance on when to use this tool versus alternatives such as recipes_get, recipes_list, or recipes_cve_search. 'Full-text search' implies the general use case, but there are no contextual cues, exclusions, or comparison to siblings, leaving the agent to infer selection criteria on its own.

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