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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds useful framing ('zero-cost, real-time', what the no-lookup mode returns) but is silent on rate limits, data freshness windows, or how 'bulk' interacts with 'export' — a behavioral question an agent will actually face.

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?

Two sentences, front-loaded with what the tool is and immediately followed by the two usage modes. No filler, no repetition of annotation-covered facts.

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 read-only query tool with a fully documented 3-param schema and no output schema, the description covers the primary lookup path well. It leaves a real gap around the third parameter combination — whether 'bulk' supersedes 'export', and what each export mode actually yields — which the agent must guess.

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 100%, so baseline is 3. The description reinforces 'lookup' semantics (IP, subnet prefix, HASSH fingerprint) and the omit-behavior, but that largely restates the schema's own parameter description and says nothing about 'bulk' or the export enum interplay.

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?

States a specific verb and resource ('Query ... threat intelligence and hostile-source indicators captured by the Citadel deception mesh') and names the two operating modes. It is clear what the tool does, though it does not position itself against any sibling (none of the listed siblings are close competitors, so this matters less).

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?

Explicitly says to pass 'lookup' for target analysis and to omit it for rolling telemetry, campaign clusters, and advisory subnets — a genuine when-to-do-what split. It gives no guidance on when to use 'bulk' or which 'export' mode to pick, and no exclusions or prerequisites.

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