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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: the search is fuzzy/token-OR-ed, spans all banks, and returns each match's owned accounts and banks. It does not state result limits or behavior on empty results.

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 core capability and search semantics are front-loaded in the first two sentences, which are tight and information-dense. The trailing sentence 'FalkorDB features: full-text index, db.idx.fulltext.queryNodes' is internal implementation detail that does not help an agent select or invoke the tool, so it does not fully earn its place.

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 helpfully describes the return shape (matches plus their accounts and banks). Combined with annotations covering safety, an agent has enough to call it correctly, but the undocumented 'k' limit and the absence of any guidance on zero-result or large-result behavior leave a small gap.

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 description coverage is 0%, so the description must carry parameter meaning and only partly does. It implies the Person/Company distinction that maps to the 'label' parameter (default 'Person'), but the 'k' limit parameter is never mentioned, leaving one of three parameters undocumented in both schema and description.

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 (fuzzy name search) and resource (customers/businesses) with explicit scope ('across all banks') and even the result payload ('the accounts and banks each one owns'). No sibling tool in the list performs entity lookup by name, so the tool is unambiguously distinguishable from graph-analytics siblings like find_rings or trace_money_path.

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 implied rather than stated: the description notes tokens are OR-ed so 'partial names work', which tells the agent how to phrase input but not when to prefer this over alternatives. There is no when-not guidance, no mention of what to do when a name is ambiguous or yields no matches, and no named alternative tool.

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