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

With no annotations, the description carries the burden of behavioral disclosure. It adds useful context by listing per-endpoint costs and global coverage, implying a paid read-only research tool. However, it does not mention return format, response structure, rate limits, or whether results are real-time or historical, leaving key behaviors undisclosed.

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 structured bullet list of endpoints that is scannable, but it is overly long and includes redundant info ('Global' appears twice, and the opening sentence is cut off: 'All end'). The list repeats pricing for each endpoint, which could be trivially redundant. It is not front-loaded with the most critical usage guidance.

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?

This is a complex tool with 23 parameters and 11 endpoints, yet the description does not explain which endpoint requires which parameters, how to choose between endpoints, or what the output looks like. There is no output schema to compensate, and the description leaves the agent to map endpoint names to parameter combinations on its own, which is a significant gap.

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 100%, so the baseline is 3. The description does not add any parameter-level details beyond what the schema already provides. It references topics like MKUltra and JFK in the schema itself, but the description only lists endpoint names without linking them to the relevant parameters, so no added value here.

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 identifies TruthPulse as a primary-source intelligence tool for FOIA releases, declassified archives, court records, forensic evidence, UAP disclosures, and conspiracy evidence. This domain focus distinguishes it from the many sibling 'pulse' tools, and the endpoint list specifies concrete actions. The verb is implied (search/retrieve), but the purpose is unmistakable.

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 given on when to use this tool versus alternatives, or how to choose among the 11 endpoints. The description merely lists endpoints with prices but does not explain which endpoint fits which scenario, prerequisites, or excluded use cases. The agent must infer usage from endpoint names alone.

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