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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered. The description adds real context beyond them: this is a Pro-tier tool and only *approved* records count toward a positive match, which materially affects interpretation of results.

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?

One front-loaded sentence carries the action, the result, and the rationale. The trailing 'is this site legit?' clause is slightly decorative but earns a little of its place by naming the intent.

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?

No output schema exists, so the description must carry return-value burden; it says only that it returns 'that record' without describing the shape or the miss case (what a negative result looks like). Adequate but incomplete for a lookup tool.

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% with a single well-described param ('A domain such as "example.co.ke" or a full URL'). The description's 'domain or URL' phrasing matches the schema but adds no format or normalization detail beyond it, so 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 precise verb+resource: given a domain/URL, report whether an approved FirmLedger record uses it and return that record. This is clearly distinguishable from sibling read tools like get_listing or search_listings, though it never names an alternative explicitly.

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 supplies a usage context ('is this site legit?' questions), which implies when to reach for it, but gives no when-not guidance, prerequisites, or named alternatives among the 35 siblings.

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