get_me

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

No annotations are provided, so the description carries the full burden. It discloses that the tool is read-only (returns information), non-mutating, and appears side-effect free (no destructive operations implied). While it doesn't detail authentication requirements or rate limits, the read-only nature and the 'etc.' acknowledging additional fields provide reasonable transparency for a getter.

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?

A single sentence that fully captures the tool's purpose with zero wasted words. It front-loads the primary function and lists the key returned fields. This is exemplary conciseness for a zero-parameter tool.

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?

The tool has a trivial input surface (no parameters) and does have an output schema, so the description's job is minimal. It adequately conveys the return content. Slight deduction: with so little required context, the description could perhaps note the read-only guarantee explicitly, but given the output schema exists, completeness is strong.

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 tool has 0 parameters, so there are no parameter semantics to describe. The baseline of 4 applies here since there are no parameters requiring documentation; the description correctly focuses on what the tool returns rather than input configuration.

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 states the verb (return), the resource (basic information about the bot), and enumerates the specific fields (id, username, name, etc.). This unambiguously distinguishes it from sibling tools like get_chat and get_chat_member_count, which target other entities.

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 bot identity/profile info, which is self-evident for a self-information tool. However, it does not explicitly state when to prefer this over get_chat (which might retrieve chat metadata), nor does it offer exclusionary guidance. For a zero-parameter self-inspection tool, the need for guidance is low, but there is no explicit context offered.

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