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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered for the agent. The description adds useful context (multi-source aggregation, dollar tallies, UEI acceptance) but says nothing about coverage windows, entity-resolution fuzziness, or partial-result behavior when no matches exist.

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?

Two sentences, zero filler. The core purpose is front-loaded and the input-format note is deliberately placed second, which is the right ordering for an agent scanning for the operation.

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?

There is no output schema, so the description carries the burden of indicating what comes back; 'dollar tallies' gestures at the aggregate output but does not describe the shape or per-source breakdown. For a single-parameter, annotated read tool this is close to sufficient, though a bit more return-format context would help.

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% and the schema's own text is terse ('Company name or UEI'), so the baseline would be 3. The description adds a real constraint the schema omits – the UEI must be 12 characters – and reinforces that exactly one entity is resolved per call.

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?

States a vivid, specific verb+resource ('Follow-the-money chain for one entity') and enumerates the exact data domains covered: federal contracts, prime->sub subaward flow, lobbying, FEC committees, and MURs. This enumeration clearly separates it from single-vertical siblings like lobbying_by_client or company_profile.

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 phrase 'for one entity' implicitly defines the usage scope and the aggregation nature suggests it is the right tool when a consolidated influence picture is needed rather than a single-vertical lookup. However, it never explicitly states when to prefer it over alternatives such as entity_relationships, dossier, or the narrower lobbying/FEC tools, and gives no prerequisites or exclusions.

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