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

Beyond the readOnlyHint/idempotentHint annotations, the description discloses that the FEC leg requires an api.data.gov key, that a failed source is noted rather than fatal, and that the result is a synthesis rather than a scored risk assessment. This unusually specific partial-failure behavior is valuable operational context.

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 dense but every sentence earns its place: core value proposition, data sources, output framing, target use cases, risk-vs-synthesis caveat, and failure behavior are all covered without filler. The most important scoping information is front-loaded in the first sentence.

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 multi-source tool with no output schema, the description does an unusually good job of enumerating what each source contributes (political committees/PACs, lobbying spend/firms/issue areas, contract/grant counts and top agencies) and how failures surface. It remains slightly generic about the actual return format ('readable map'), but combined with the complete input schema, this is enough for correct selection and invocation expectations.

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 schema already documents organization, company, state, and year clearly. The description adds no parameter-specific syntax or constraints beyond what the schema provides, which is acceptable given the high schema coverage but means the description itself contributes little on this dimension.

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 defines the tool as a one-call cross-source map for an organization and explicitly names the three federal record streams it joins: FEC, Senate Lobbying Disclosure Act, and USAspending. It also states the core output framing—money flowing OUT to influence versus money flowing IN from federal awards—and distinguishes itself from counterparty_risk_score.

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 gives explicit target use cases (investigative journalism, govcon, due-diligence research) and explicitly says it is an informational public-record synthesis, not a risk score, which helps differentiate it from counterparty_risk_score. It does not enumerate alternatives among other organizational-research siblings, but the context is sufficient for most selection decisions.

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