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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real context beyond them: the tool reuses a pre-built spendquery.com page when one exists (fast) versus constructing it (5-15 s), and it rolls up all registrations into a single yearly money view. It does not mention caching staleness or rate limits, so it falls short of 5.

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 purpose is front-loaded in the first clause, which is good, but the sentence then runs long enumerating return sections that an output schema already covers, making it dense and hard to scan. The latency caveat is useful and earns its place; much of the section list does not.

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 lookup with full annotations and an output schema, the description supplies what an agent still needs: what the profile aggregates, that registration and exclusion data are included, and that latency can vary from fast to 15 seconds. Return-value detail is rightly left to the output schema, so completeness is strong though not exhaustive.

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?

There is a single parameter and the schema already documents it fully at 100% coverage, including UEI format and name/ticker examples. The description adds no resolution or ambiguity guidance (e.g. what happens on ambiguous names or ticker/UEI collisions), so it sits at the baseline for a well-documented schema.

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 a specific resource and scope — the full federal profile of a single company — and enumerates the sections returned (federal money by year, agencies, industries, SAM.gov registration, exclusions, state payments, brief, spendquery page). An agent can tell this is the consolidated lookup rather than a search or award-level tool. It stops short of naming which sibling (e.g. search_recipients) to use for a different scope, which keeps it at 4.

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?

"One company in one call" implies the when-to-use case (a single entity, comprehensive view), but there is no explicit contrast with siblings like search_recipients or award_prices and no stated exclusions. The only concrete guidance is an operational note: it prefers the prebuilt site page when available and otherwise builds it in 5-15 s.

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