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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Get', implying a read-only operation, but does not mention potential side effects, rate limits, response size, or any special handling. For a knowledge-base retrieval tool, the agent has no indication of what to expect in terms of data volume or formatting.

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 description is a single, front-loaded sentence that immediately states the purpose and then lists the key contents. Every word earns its place with no fluff or repetition. It is efficiently structured for quick scanning.

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 parameterless getter with no output schema, the description provides sufficient context by listing the main knowledge areas an agent will receive. It does not explain the return format or whether the response is large, but given the simplicity and the absence of an output schema, this is acceptable. It is nearly complete for the tool's straightforward nature.

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 has zero parameters, so the schema is trivially complete. Per the rubric, a zero-parameter tool gets a baseline of 4, and the description correctly adds no unnecessary parameter details. There is nothing more to explain.

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 clearly states the tool retrieves the aggregated NMLP Knowledge Base and enumerates its major content areas (donor archetypes, routing tracks, condition grades, decision framework, donor glossary, coverage tiers). This provides a specific verb+resource and distinguishes it from query-oriented tools like nmlp_search_qa, though it doesn't explicitly contrast with overlapping siblings like nmlp_get_pillar_guides.

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?

No guidance is given on when to use this tool versus alternatives. The description only states what it does, not when an agent should select it over siblings such as nmlp_search_qa or nmlp_get_pillar_guides. There are no conditions, exclusions, or recommended usage patterns.

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