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 explains the return type (list of collections/threats) and clarifies that threat actors are modeled as collections, which adds useful context. However, it doesn't disclose behavioral traits like authentication needs (implied by api_key parameter), rate limits, or error handling, leaving gaps for a mutation-free but API-dependent 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 (overview, usage note, parameter details, return value) and uses bullet points for readability. It's appropriately sized, though the parameter explanations could be slightly more concise. Every sentence adds value without redundancy.

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 (4 parameters, no annotations, but with output schema), the description is mostly complete. It explains the purpose, parameters, returns, and workflow integration. The output schema likely covers return values, so the description doesn't need to detail them. However, it misses the 'api_key' parameter and lacks behavioral details like error cases or pagination.

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 adds meaningful semantics for 'query' (search query to find threats), 'limit' (number of threats to retrieve, default 10), and 'order_by' (sorting options with syntax and defaults). However, it omits the 'api_key' parameter entirely, which is a notable gap given its importance for authentication.

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 for threat actors in the Google Threat Intelligence platform, specifying the resource (threat actors/collections) and action (search). It distinguishes from siblings like 'search_threats' by focusing specifically on threat actors, though it doesn't explicitly contrast with all similar tools.

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 clear context by explaining that results from this tool can be used with 'get_collection_report' for full reports, offering a specific workflow. However, it doesn't explicitly state when to use this versus alternatives like 'search_threats' or 'search_campaigns', nor does it mention any exclusions or prerequisites.

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