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

With no annotations, the description carries the full burden. 'Get' plus the zero-parameter schema implies a safe read, and the description discloses the card's contents, which is genuinely useful. However, it says nothing explicit about read-only behavior, caching, or response format beyond the enumerated fields.

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?

Front-loaded with the core purpose, but the single run-on paragraph packs in drop-box logistics, load-size handling, phone instructions, and language policy. With no output schema these details arguably explain returns, yet the density and embedded instructions reduce crispness.

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 zero-param getter with no output schema, the description reasonably covers what the card contains. It is close to complete for the agent's needs, though it could more clearly frame these as returned fields rather than instructions.

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?

The tool takes zero parameters, so the schema cannot supply parameter meaning; baseline is 4. The description correctly adds no parameter noise and instead explains the returned entity data.

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 and resource ('Get NMLP's canonical business entity card') and enumerates the fields it returns (address, phone, services, area served, languages, drop box). Clear purpose, but it never contrasts itself against siblings like nmlp_get_knowledge or nmlp_get_donation_options, so differentiation is left to inference.

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 explicit when-to-use or when-not-to-use this tool versus the many sibling lookup tools. The operational details (warehouse hours, texting 505-250-3804, Spanish replies) describe NMLP's real-world services, not when an agent should call this tool.

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