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

No annotations exist, so the description carries the full burden. It does add real value by naming upstream data provenance (USASpending, EU Horizon) and by framing coverage as 'disclosed'/'awarded' data, but it says nothing about result granularity, historical depth, or what happens when the organization name does not resolve.

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 leading verb+resource statement is well front-loaded, but the second sentence largely restates the first ('lobbying expenditures... R&D grants' repeated verbatim). Only the exclusion clause in that sentence earns its place.

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 single-parameter, read-only lookup with no output schema or annotations, the description covers what data domains are returned, where they come from, and how it differs from the tenders sibling. A brief note on return shape or coverage limits would close the remaining 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 coverage is 100% and the organization_name field already specifies the acceptable entity types and exactness requirement. The description's 'for a specific organization' adds only marginal framing beyond the schema, so the baseline 3 applies.

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 specific verb ('Track') plus three concrete resource types (lobbying expenditures, registered lobbyists, government R&D grants) and names the data sources (USASpending, EU Horizon). Sibling differentiation is explicit via the searchGovernmentTenders pointer.

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?

Gives an explicit 'Use when' condition tied to a specific organization and an explicit 'Do not use' exclusion that names the alternative tool (searchGovernmentTenders) for open procurement tenders. Nothing is left to inference about routing.

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