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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about authentication, rate limits, or what happens when the profile is not found. The only behavioral content is a boilerplate '200 Successful Response' line that adds no real context about the data returned.

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 sentence is tight and front-loaded, but the trailing '### Responses: **200** ... Content-Type: application/json' block is auto-generated noise that does not help an agent decide or invoke. Half the text is boilerplate rather than substance.

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 simple two-parameter read tool with no output schema and no annotations, the description is minimally adequate. However, it never indicates what a profile contains or how a missing/unknown platform is handled, which is the main gap an agent would hit at call time.

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 100%, so the two parameters are already documented in the schema, and the description only restates them at a high level. It adds no format hints for platform (no enum, no list of accepted values) or for user_id, which would have been genuinely useful given the free-form string typing.

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 a specific verb and resource ('Get IM user profile') and pins the lookup key ('by user ID on a specific platform'). It is clearly distinguishable from lookup-style siblings like get_im_channel_by_channel_id, though it does not explicitly contrast itself with search_im_profiles.

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 only implied: the agent can infer this is the direct-lookup path when it already holds a platform and user_id. There is no explicit when-to-use, when-not-to-use, or mention of search_im_profiles as the alternative for discovery-style queries.

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