getChatMenuButton

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

With no annotations, the description carries the behavioral disclosure burden. It discloses the operation is a read ('Get'), specifies the returned object type, and clarifies the default behavior when chat_id is omitted. This is sufficient for a simple, non-mutating getter, though it does not discuss potential errors or edge cases.

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 sentence that front-loads the action and includes the essential scope and return type. Every part earns its place, with no redundant or vague wording.

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 one-optional-parameter getter with no output schema, the description is complete: it states what the tool returns, what the parameter means, and the default behavior. An agent has enough information to invoke this tool correctly.

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?

There is only one optional parameter and schema description coverage is 100%, so the schema already documents chat_id adequately. The description adds minimal semantic value beyond the schema, only reinforcing that the chat is private and that omitting chat_id returns the default menu button.

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 a specific verb and resource: 'Get the current value of the bot's menu button' with explicit scope ('in a private chat, or the default menu button'). It also names the return type, making the tool's purpose unambiguous and distinct from the sibling setChatMenuButton.

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 provides clear context for when to call it—retrieving a menu button value rather than modifying it—and it describes the optional chat_id behavior. It does not explicitly name setChatMenuButton as the alternative for setting, but the get-versus-set distinction is obvious from the tool name and sibling list.

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