telegram-get-profile

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description adds marginal value by listing specific fields. It does not disclose additional behavioral traits such as rate limits or potential return format, but it is consistent with annotations and provides context on expected data content.

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 description is a single, concise sentence (16 words) that front-loads the verb and resource. Every word serves a purpose: it states the action, the resource, and lists key included fields with 'and more' for completeness. No unnecessary information.

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?

Given the tool's simplicity (one required parameter, readOnlyHint, openWorldHint, no output schema), the description is largely complete. It lists specific fields users can expect, compensating for the lack of an output schema. It could briefly mention the return format (e.g., JSON object) but this is not critical for agent invocation.

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?

The input schema covers the single parameter 'userId' with a clear description ('User ID or username'). Since schema_description_coverage is 100%, the baseline is 3. The tool description does not add further parameter semantics beyond what the schema provides.

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 clearly specifies the action ('Get') and resource ('detailed profile info of a Telegram user') and lists specific included fields (bio, birthday, premium status, business info). It distinguishes itself from sibling tools like telegram-get-chat-info which focus on chat-level data.

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?

The description implies usage for retrieving user profile information but does not provide explicit guidance on when to use this tool versus alternatives like telegram-get-chat-info or telegram-get-contacts. No when-not-to-use or exclusion criteria are given.

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