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

No annotations exist, so the description carries the full burden, and it does establish that this is a passive informational lookup whose content includes a specific policy (wet books stay out of the box, box-full escalation). However, most of the text describes the *data* the card contains rather than the tool's behavior — it never states whether the call is read-only, whether it hits live data, or what the response shape is, which is the gap for an unannotated tool.

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 first sentence covers the payload and is well front-loaded, but everything after the colon is payload content dumped into the definition — drop-box location, unloading hours, a phone number, and language handling. 'Box full? Text or call 505-250-3804' and 'Unit A is only the business address' do not help an agent select or invoke the tool and bloat the definition considerably.

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 must convey what comes back, and it does so thoroughly by enumerating the card's fields and even the policy nuances an agent would otherwise have to rediscover. It falls short of 5 only because it never indicates the return format (structured object vs. prose) or how the card content is keyed, so an agent knows *what* is returned but not *how*.

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 are zero input parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies no arguments are needed by framing the tool as a fixed canonical card lookup.

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 verb and resource ('Get NMLP's canonical business entity card') and enumerates the fields returned (address, phone, services, area served, languages, conditionPolicy, dropBox), which lets an agent distinguish it from siblings like nmlp_get_donation_options or nmlp_schedule_pickup. It loses the fifth point because the opening clause is buried under a long run-on sentence about drop-box logistics rather than cleanly stating the tool's single purpose.

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?

Usage is only implied: the content list suggests this is the tool for contact/location/service-area questions, and mentions of pickups hint that nmlp_schedule_pickup is the alternative for large loads. There is no explicit when-to-use/when-not statement and no sibling is named as an alternative, so an agent must infer routing from the payload description.

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