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

The description discloses that the tool is on a roadmap and returns 'not_implemented per state', which is a key behavioral trait. However, with no annotations provided, the description should also mention other behaviors like authentication requirements or data freshness, which are absent.

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 very short and to the point, with no wasted words. The key information (purpose, roadmap status) is front-loaded. The parameter list follows. It earns its place, but could be slightly more structured with separate sections.

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?

Given the tool has no output schema and the description fails to explain what the agent should expect in the response (even a 'not_implemented' message), it lacks completeness. An agent would not know how to handle the result or whether to retry. Additional context about the roadmap status and potential alternatives is needed.

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 schema has 0% description coverage, so the description adds basic meaning by naming the two parameters and providing brief explanations ('Name of the debtor', '2-letter state code'). This is minimal but incremental over the schema which only has titles. More detail like format or examples would improve the score.

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 states 'UCC lien lookup' which clearly identifies the tool's purpose. It distinguishes from siblings like 'mcp_get_company_details' by specifying a different domain (UCC filings). However, the 'Roadmap; returns not_implemented per state' indicates it's not fully functional, slightly reducing clarity for an agent deciding whether to use it.

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 explicit guidance on when to use this tool versus alternatives like 'mcp_get_company_details' or 'mcp_search_companies'. The only hint is that it returns 'not_implemented', which implies it should not be used for actual lookups, but no alternative tool is suggested.

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