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

With no annotations, the description carries the behavioral burden and does the single most important thing: it discloses that the tool is unimplemented and returns not_implemented. It does not describe auth, rate limits, or result shape, but the key behavioral fact is stated plainly.

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?

Two tight lines with the status caveat front-loaded right after the purpose, so an agent sees the stub warning immediately. Only the Args block, which merely mirrors the schema, is low-value filler.

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 roadmap stub with two required params and no output schema, the description states enough: what it does, that it is unimplemented, and the parameter set. No return-value detail is needed given the not_implemented behavior is spelled out.

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 0% and both parameters are required, so the description must compensate. It names both parameters and adds one piece of real meaning ('2-letter state code' format), but gives no format or matching semantics for debtor_name. Minimal but non-zero value beyond the 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?

Names a specific resource (UCC lien filings) and the lookup action, which clearly separates it from siblings like mcp_search_court_cases and mcp_search_sec_filings. It is a noun phrase rather than a verb-led statement, but the intent is unambiguous.

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 parenthetical '(Roadmap; returns not_implemented per state.)' is an explicit when-not-to-use signal: the agent learns the tool is a stub and will yield no data. It does not point to an alternative tool for the same need, so it falls short of a full 5.

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