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

No annotations are supplied, so the description carries the full burden. It implies a read-only search but says nothing about permissions, rate limits, result caps, or whether paging is required to see all matches; the 'Responses: 200 Successful Response' block is pure boilerplate that discloses no behavior.

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 two substantive sentences are tight and front-loaded, but the appended 'Responses: 200 Successful Response / Content-Type: application/json' block is auto-generated noise that earns no place and dilutes the useful content.

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 five-parameter search tool with no annotations and no output schema, the description omits result shape, pagination behavior, date-filter semantics, and any limits. An agent could invoke it but could not predict whether it must page through results or how the returned documents are structured.

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 60%: email, gte, and lte are documented in the schema, but page and page_size have no descriptions at all. The description adds no meaning to any of the five parameters — it never mentions date filtering, pagination, or default page size, so it fails to compensate for the coverage gap.

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 gives a specific verb and resource ('Search Vysion for documents') plus the exact matching criterion ('containing or linked to an email address'), which implicitly separates it from get_documents_by_phone or get_documents_by_tag. It never names an alternative explicitly, so it stops short of full sibling differentiation.

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?

'Use for OSINT and identity investigation' signals a usage context but is a broad domain label, not a decision rule. There is no statement of when to prefer this over search_documents or the other get_documents_by_* tools, and no exclusions or prerequisites.

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