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

Annotations already declare readOnlyHint=true and idempotentHint=true, which the description neither contradicts nor repeats. The description adds useful behavioral context by specifying that the tool returns workflow guides and reference documentation across four topics, clarifying content scope and what the user can expect. It doesn't overpromise or hide side effects, and the output schema covers return-value details.

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?

The description is exactly two sentences: the first states the purpose and primary usage, and the second compactly lists the four topics with parenthetical summaries. It is front-loaded and every sentence earns its place; there is no fluff or redundancy.

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 tool's simplicity (one optional parameter, strong annotations, and an output schema), the description is fully adequate. It covers what the tool does, when to use it, and what topics are available, while the schema and annotations handle parameter details and safety. No critical contextual gap remains.

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 input schema has a single optional parameter 'topic' with an enum and a description that already explains each allowed value (overview, automation, strategies, selection). The tool description repeats the same topic list with parenthetical explanations, but adds little beyond the schema's own descriptions. With 100% schema coverage, the baseline 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?

The description clearly states 'Get Arcadia workflow guides and reference documentation', combining a specific verb ('Get') with the resource ('workflow guides and reference documentation'). It distinguishes this tool from sibling read_* tools by being the only one focused on documentation/guides, and it enumerates the covered topics (overview, automation, strategies, selection).

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 explicitly says 'Call this before multi-step workflows' and gives concrete examples ('opening LP positions, enabling automation, closing positions') and use cases ('when you need contract addresses, asset manager addresses, or strategy parameters'). However, it doesn't name alternative tools or specify when not to use it, so it falls short of a perfect 5.

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