cfpb_complaints

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds only a public-domain legal citation, not what the call returns, whether results are paginated or capped, or how the live CFPB API behaves (latency, error modes).

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?

It is a single short sentence with no padding beyond the statutory parenthetical, which supports public-domain use but consumes space that could have described the operation. It is front-loaded but under-informative rather than efficient.

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?

With no output schema, the description carries the burden of explaining return values, and it says nothing about what a complaint audit yields. For an open-world remote lookup, the agent lacks enough context to know what to expect or how to interpret results.

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 single 'company' parameter already has an example ('Equifax'), so the schema does the heavy lifting. The description adds nothing about name matching, aliases, or partial-match behavior for that parameter, leaving the baseline 3.

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 names the resource (CFPB consumer financial complaints) but pairs it with the vague verb 'audit', so it is unclear whether it retrieves complaints, counts, or scores them. It also does not distinguish this tool from related siblings such as fdic_bank_health or gleif_lei_kyb.

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?

There is no when-to-use guidance, no stated prerequisites, and no mention of alternative tools for financial-institution research. The agent must infer from the name alone that this is a lookup by company.

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