answerWebAppQuery

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

With no annotations, the description carries the full burden of disclosure. It directly states the main side effect — sending a message on behalf of the user to the originating chat — and mentions the success return type. It does not cover permission prerequisites or failure behavior, but the core send-on-behalf-of-user behavior is explicit.

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 dense sentence with no filler, front-loading the action and side effect before noting the return value. Every clause contributes useful 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?

For a two-parameter tool with a nested object and no output schema, the description provides essential context: the query originates from a chat, the message is sent on behalf of the user, and a SentWebAppMessage object is returned on success. It could add an explicit note about permission requirements or one-time answering, but it is largely complete.

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 description coverage is 100%, so the schema already documents web_app_query_id and result. The description adds no parameter-level detail beyond what the schema provides; mentioning 'result' and 'message' is consistent but redundant.

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 opens with a specific verb phrase, 'Set the result of an interaction with a Web App,' and identifies the unique resource: a Web App query. It also clarifies that a message is sent on behalf of the user to the originating chat, which distinguishes it from sibling answer*Query tools such as answerCallbackQuery and answerInlineQuery.

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 conveys a clear context: use this tool when a Web App interaction has produced a query that must be answered and the resulting message should be sent to the originating chat. It does not explicitly name alternatives or exclusions, but the context is specific enough to route an agent correctly.

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