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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, covering the safety profile. The description adds only the raw endpoint path 'GET /api/v2/strategy/reaction/llm/folder/{id}', which is essentially a restatement of the name and discloses nothing new (no return shape, no error or not-found behavior).

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, front-loaded with the purpose before the endpoint. Nothing is padded, though the endpoint clause is low-value filler rather than earning its place.

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 single-parameter read lookup with annotations covering safety and no output schema, the description is minimally sufficient. It still omits any differentiation from the sibling folder/root variants and any indication of what is returned, so it is adequate but not 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% and the single 'id' parameter is documented as 'Folder ID' in the schema. The description adds no format, ID-type, or sourcing detail beyond that, so the baseline 3 applies.

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 ('Get LLM reaction folder by ID'), so the agent knows it retrieves a single folder entity. However, it never distinguishes itself from near-identical siblings like get_strategy_reaction_llm_folder or get_strategy_reaction_llm_folder_root, leaving the agent to infer the difference from names alone.

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?

There is no when-to-use guidance, no prerequisite (e.g. needing an existing folder ID), and no mention of alternatives. The description only restates what the tool fetches, so the agent gets no routing help among the many folder-related siblings.

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