telegram-get-message-buttons

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds that the tool returns markupType='none' when no keyboard, which is a behavioral detail. It does not add much beyond annotations and does not contradict them.

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 three sentences that efficiently convey purpose, usage, and output details. The first sentence is packed but well-structured. It is front-loaded with key 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?

The description explains the return format (buttons with indices, type, label, type-specific fields) and behavior when no keyboard exists. For a tool with simple parameters and no output schema, this is fairly complete. It also connects to the 'press-button' workflow.

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?

Both parameters (chatId, messageId) are fully described in the schema with clear descriptions. The tool description does not add additional meaning beyond the schema, so baseline 3 is appropriate.

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 tool lists inline/reply keyboard buttons with indices, type, label, and type-specific fields. It distinguishes itself from the sibling tool 'telegram-press-button' by positioning itself as a helper to call first.

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 explicitly says 'Helper for telegram-press-button — call this first to discover indices and filter by type before pressing'. This provides clear when-to-use context and implies when not to use it (when no keyboard, returns markupType='none').

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