Google Threat Intelligence MCP Server

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

With no annotations provided, the description carries the full burden. It discloses that results are collections and mentions ordering options with defaults, but doesn't cover important behavioral aspects like pagination, rate limits, authentication needs (though 'api_key' is in schema), error handling, or what constitutes a 'threat report' in detail. It adds some context but leaves gaps for a search tool.

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 clear sections: purpose, platform context, usage note, parameter details, and return value. It's front-loaded with the core function. Some sentences could be tighter (e.g., the second sentence about Google Threat Intelligence is somewhat redundant), but overall it's efficient and informative.

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 moderate complexity (search with 4 parameters), no annotations, and an output schema (implied by 'Returns' statement), the description is reasonably complete. It covers purpose, parameters, and output format, though it could benefit from more behavioral context (e.g., authentication, errors). The presence of an output schema reduces the need to detail return values.

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%, so the description must compensate. It explains all 3 user-facing parameters (query, limit, order_by) with semantics, defaults, and formatting rules (e.g., '+' for ascending). The 'api_key' parameter is not mentioned in the description, but since it has a default of null and is likely for authentication, this omission is acceptable. The description adds significant value beyond the bare schema.

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 searches threat reports in the Google Threat Intelligence platform, specifying the resource (threat reports) and action (search). It distinguishes from siblings by mentioning the specific type of search (threat reports vs. campaigns, IOCs, etc.), though it doesn't explicitly contrast with all similar tools like 'search_threats'.

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 provides some usage context by mentioning that results are collections and can be used with 'get_collection_report' for full details, implying a workflow. However, it lacks explicit guidance on when to use this tool versus alternatives like 'search_threats' or 'search_campaigns', and doesn't specify prerequisites or exclusions.

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