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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, and the description mostly repeats the read-only aspect. It does not explain sanitization behavior, what the feed returns, what happens to supplied text, or any rate limits or auth requirements.

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 a single compact sentence with no wasted words, and it front-loads the read-only nature of the tool. However, the compound phrase is dense and mixes two functions, which slightly weakens structure.

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?

With no output schema and no return-value explanation, the description should clarify what an agent receives, but it does not. It also leaves the only parameter undocumented, so the definition is incomplete for even a low-complexity tool.

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?

The single optional parameter text_to_sanitize has 0% schema description coverage and is never mentioned in the description. The phrase 'prompt-injection sanitization' hints at its purpose at best, but the description provides no meaning, format, or expected input semantics for the parameter.

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 is a noun phrase that conflates a read-only threat feed with prompt-injection sanitization, so the actual operation is unclear. Because the schema contains a text_to_sanitize parameter, an agent cannot tell whether the tool retrieves threat intel, sanitizes supplied text, or does both.

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?

There is no guidance on when to use this tool versus its siblings such as pulse_arb_routes or pulse_base_liquidity. The only implied context is that it is security-related, but no prerequisites, alternatives, or exclusions are stated.

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