get_my_commands

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety profile. The description adds 'current' indicating a snapshot, but does not disclose details about default scope, language behavior, or response format. Annotation coverage lowers the bar, yet the description adds minimal behavioral context.

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, front-loaded sentence of six words. Every word carries meaning, and there is no fluff or repetition.

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?

Without an output schema, the description only says 'command list,' which gives a vague hint. It does not explain the two parameters, the return structure, or potential empty results. For a simple getter, this may be passable, but the lack of parameter clarity and output details makes it incomplete.

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 schema describes two parameters (scope, language_code) with 0% coverage, and the description completely omits any mention of them. The agent has no guidance on what scope means (likely a BotCommandScope object) or how language_code affects output. This is a significant gap that the description fails to compensate for.

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 action ('Get') and the target ('the bot's current command list'). It is specific enough to distinguish from sibling tools like set_my_commands (which modifies commands) and get_my_name (which retrieves a different resource).

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 the tool is for retrieving the current command list, which gives clear usage context. However, it does not explicitly mention when not to use it or point to alternatives like set_my_commands. Given the simple read-only nature, the implied usage is clear but no exclusions are stated.

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