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

Annotations already declare destructiveHint=true and readOnlyHint=false, so safety is covered. The description adds only the raw HTTP route, saying nothing about irreversibility, cascade effects on dependent sessions/webhooks, or auth requirements.

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?

Two short sentences with no padding; the action is front-loaded. The HTTP verb/path is of limited value to an agent but is a compact convention, not bloat.

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 destructive mutation with no output schema and an entirely undocumented parameter, the description should explain what is deleted and with what consequence. It does neither, leaving the agent to guess at scope and reversibility.

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 coverage is 0% for the single required parameter 'id', and the description does not compensate. The route template hints that id sits in the path, but the description never says whether it is a reaction id, session id, or something else, or what format it takes.

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?

States a specific verb and resource: 'Delete LLM reaction'. This clearly distinguishes it from the get_/put_/post_strategy_reaction_llm_id siblings. It stops short of any scoping detail, but the core purpose is unambiguous.

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?

No when-to-use guidance, no prerequisites, no exclusions, and no mention of related tools such as put_strategy_reaction_llm_id_reset or the folder variant delete_strategy_reaction_llm_folder_id. The agent must infer everything.

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