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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds only the REST endpoint path and the fact that a full collection is returned; it says nothing about result shape, ordering, or whether the list is flat or tree-structured.

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 terse fragments, purpose front-loaded, nothing padded. The trailing 'GET /api/v2/strategy/code/folder' is marginally redundant for an agent but costs little.

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 simple no-arg listing tool the description is minimally adequate, but with no output schema it leaves the return structure undefined and does not clarify how the result differs from the _id and _root variants. Enough to call correctly, not enough to use confidently.

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 tool takes zero parameters, so the baseline of 4 applies. The description implies an unfiltered full-collection read, which is consistent with the empty 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?

States a clear verb (get) plus resource (code strategy folders) and the scope 'all', which implicitly separates it from siblings like get_strategy_code_folder_id (single item) and get_strategy_code_folder_root (root only). It does not, however, name or explicitly contrast those siblings, so an agent must infer the boundary.

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 and no mention of alternatives, despite a dense cluster of adjacent tools (get_strategy_code_folder_id, get_strategy_code_folder_root, get_strategy_code_total). The agent gets no signal about which retrieval variant to pick.

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