inline_query

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

Discloses key behaviors: can either list results or send a result depending on send_to parameter. Explains result_index for selecting a result. With no annotations, the description carries full burden and does well in explaining the conditional behavior. Could mention rate limits or bot availability but not essential.

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?

Efficient one-sentence purpose followed by a clear, bulleted list of parameters. Every sentence adds value; no unnecessary words.

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 presence of an output schema (not shown), the description fully explains all input parameters and the tool's conditional behavior. It is complete enough for an agent to correctly invoke the tool.

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?

Schema has 0% description coverage, so description fully compensates by explaining each parameter: bot expects @username or ID, query is search term, limit sets max results, send_to determines where to send or just list, result_index selects which result, reply_to replies to a message. Adds crucial context missing from schema.

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?

Description clearly states it sends an inline query to a bot (equivalent to typing @bot keyword) and can send a result. It distinguishes itself from sibling tools like start_bot or send_message, which perform different actions.

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?

Describes the inline query mechanism and provides context for when to use it (to query a bot inline). However, it does not explicitly state when not to use it or mention alternative tools. The context is clear but lacks explicit exclusions.

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