Search Tags

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

The description adds meaningful behavior beyond the annotations: it discloses that searching is client-side over a cached list, explains the matching modes, and notes that no filters returns the full tag set. Annotations already declare read-only/open-world behavior, and the description does not need to repeat that.

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 compact and front-loaded, moving from the operation and data source to per-parameter matching semantics and default behavior. Every sentence carries useful information with no redundant restatement.

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 simple four-optional-parameter search surface, the presence of an output schema, and annotations covering safety behavior, the description supplies everything needed to invoke the tool correctly. It covers the data source, all matching semantics, and the no-parameter default.

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 already 100%, but the description adds matching semantics that the schema does not fully convey: query is a substring match across name/description/slug/label, category and intention are exact case-insensitive matches, and cve substring-matches associated CVEs. It also clarifies that all parameters are optional.

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 states a specific verb and resource: search GreyNoise tags, operating client-side over the cached v3/tags list. This clearly separates it from a generic tag-list or tag-detail tool, though it does not explicitly name a sibling alternative.

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?

It explains that all parameters are optional and that omitting them returns every tag, which gives useful usage context. However, it does not explicitly say when to use this instead of siblings such as get-tag-list or get-tag-details, so the guidance is implied rather than explicit.

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