truthpulse

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

No annotations are provided, so the description must fully disclose behavior. It describes the tool as querying databases but does not mention whether actions are read-only, any authentication needs, rate limits, or side effects. The marketing language ('No spin') does not convey technical behavior.

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 structured with a header, coverage line, and bulleted list of endpoints. It is reasonably concise but contains some redundancy (e.g., 'Global' mentioned twice) and could be shorter. The front-loading is adequate.

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 has 23 parameters and no output schema or annotations, the description lacks explanation of typical usage flows, output format, or how to combine parameters. The endpoint list is helpful but insufficient for a complex tool with many parameters.

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% with descriptions for all 23 parameters. The description adds value by grouping endpoints and noting pricing ($0.10 each), which gives context beyond the schema. However, it does not elaborate on parameter interactions or defaults, so the improvement over schema is moderate.

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 provides intelligence from FOIA releases, declassified archives, court records, etc., and lists specific endpoints. It distinguishes from sibling 'pulse' tools by focusing on evidence and conspiracy topics. However, it lacks a concise verb+resource statement, mixing multiple purposes.

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 enumerates endpoints and gives prices, implying usage contexts for each. It says 'Evidential-first. No spin. Global.' but does not explicitly state when to use this tool over siblings or exclude scenarios. The listing provides implicit guidance but no clear 'use this when' statement.

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