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

No annotations are provided, so the description carries the full behavioral burden. It confirms this is a read/search operation and states the platform scope, but says nothing about pagination behavior despite page/page_size parameters, nothing about auth requirements, rate limits, or result ordering, and the '200 Successful Response' block is generic OpenAPI boilerplate rather than meaningful behavioral disclosure.

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 first sentence is efficient and front-loaded, but the trailing 'Responses: **200**... Content-Type: application/json' block is copy-pasted API-listing noise that consumes roughly half the description without informing tool selection or invocation.

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 6-parameter search tool with no annotations and no output schema, the description omits too much: pagination semantics, date-range filtering purpose, result limits, and the difference between this and the ID-based profile lookup. The presence of gte/lte is never even acknowledged, so an agent must reverse-engineer the tool from the schema alone.

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 67%, with q, gte, lte and platform already described in the schema and only page/page_size undocumented. The description adds no semantics for any parameter — 'keyword' loosely maps to q and 'Telegram or Discord' merely restates the platform enum already present in the schema, while the date-range parameters gte/lte go entirely unmentioned.

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 opens with a specific verb and resource ('Search Vysion's IM database for user profiles by keyword') and names the return shape ('matching Telegram or Discord user profiles'). It implicitly separates itself from the channel/message search siblings by saying 'user profiles', though it never explicitly contrasts with get_im_profile_by_user_id.

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?

There is no guidance on when to use this keyword search versus the direct-lookup sibling get_im_profile_by_user_id, nor any stated prerequisites or exclusions. The agent can only infer usage from the phrase 'by keyword', which is a weak substitute for explicit routing guidance.

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