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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Find threat patterns across incidents' without explaining what inputs are expected, what data sources are queried, what the output looks like, or any operational constraints. An agent cannot infer whether it should pass an IP, domain, keyword, or some other form of query.

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 entry is extremely short, which technically satisfies conciseness, but it is under-specified rather than economical. The description redundantly begins with 'Threat Pattern:' which repeats the tool name, and the remainder adds little beyond the title. It is a single sentence with no structure that would help an agent quickly parse key usage details.

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?

Despite having only one parameter and an output schema, the description is inadequate for a threat-intel lookup tool. It fails to clarify what 'threat patterns' are, what kind of input the 'q' parameter accepts, or what the returned data represents. An agent would be guessing at both the correct invocation and the interpretation of results.

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 description coverage is 0% and the description does not mention the 'q' parameter at all. There is no indication of how the query string is interpreted or what format it should take. The schema itself merely declares a string with a default of empty, so the agent is left without any meaningful guidance on parameter usage.

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 ('Find') and resource ('threat patterns across incidents'), which is clear enough to distinguish it from unrelated siblings like 'ascii85' or 'weather'. However, it does not explicitly differentiate it from closely related threat-intel tools such as 'threat_actor', 'ioc_reputation', or 'malware_family', so it is not uniquely disambiguated.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any exclusions, prerequisites, or scenarios where a sibling tool would be more appropriate. The only implied usage is that it is for finding threat patterns, but this is not developed into actionable selection criteria.

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