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

No annotations are supplied, so the description carries the full behavioral burden. It implies a read-only search but says nothing about permissions, result ordering, pagination behavior despite page/page_size parameters, or what a match actually contains.

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 front-loaded and efficient, but the trailing 'Responses: 200 Successful Response / Content-Type: application/json' block is API-spec boilerplate that adds no selection value and pads the definition.

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 annotations, no output schema, and seven parameters, the description should explain at minimum what a result looks like and how paging works. It omits both, leaving an agent unable to predict the response shape for an investigative search tool.

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 71%, so the schema documents most parameters itself. The description adds only a brief 'Filter by platform, username, date' mapping, leaving q's query syntax and page/page_size behavior unexplained.

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 and resource ('Search Vysion's IM database for messages') and scopes it to chat platforms including Telegram and Discord, which distinguishes it from siblings like search_im_channels or search_im_profiles. It does not explicitly name those siblings, so it falls short of a 5.

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?

'Primary tool for chat investigation' implies the usage context, but there is no explicit when-to-use/when-not guidance and no mention of alternatives such as search_im_channels or search_email_in_im_database. Usage must be inferred from the phrase 'Primary tool'.

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