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

With no annotations, the description carries full responsibility for behavioral disclosure. It does mention 'identity limitations' and a cost of 0.006 USDC, but it does not state whether the operation mutates state, requires authentication, has rate limits, or what outcomes an agent should expect.

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 text is short but reads as a noun-phrase fragment rather than a usable definition. It front-loads no actionable information, and the cost/limitation details are appended without explanation, so brevity comes at the expense of substance.

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 three parameters, a nested object, no output schema, and dozens of sibling tools, this description is far too sparse. An agent cannot determine how to construct a valid request, what response to expect, or how this tool fits among its alternatives.

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% and the description does not mention query, subject, or source_urls. The required source_urls parameter is undocumented, and the nested subject object is entirely unexplained, so the agent cannot infer parameter semantics from either source.

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 identifies the tool's domain (public social-source observations) and mentions attribution and identity limitations, but it lacks a verb stating what the tool actually does – e.g., fetch, verify, or record evidence. Without that, an agent cannot determine how it differs from siblings like fetch_evidence, source_backed_search, or onchain_evidence.

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 rather than the many evidence-related siblings. The only contextual clue is the 0.006 USDC price, which implies a paid operation, but no selection criteria, prerequisites, or exclusion conditions are stated.

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