read_guides

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety is covered; the description adds the valuable sequencing trait that this should be fetched ahead of multi-step flows. It stops short of describing output size/shape, but an output schema exists to cover that.

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?

Front-loaded with the action and the precondition in the first two sentences. The trailing topic list duplicates the enum descriptions, so it is slightly longer than strictly necessary, but no sentence is pure filler.

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 optional-enum documentation tool with 100% schema coverage and an output schema, the description supplies everything an agent needs: what it returns, when to invoke it, and how to pick a topic.

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 100% with an enum and per-value descriptions, so the baseline is 3. The description adds marginal value by framing each topic by its use case (e.g., 'selection – how to evaluate and parameterize strategies'), though it largely restates the enum.

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 Arcadia workflow guides and reference documentation') and enumerates the concrete content available (addresses, catalog, templates, parameters). It is clearly distinguishable from the read_/write_ data tools in the sibling list, which return live state rather than guidance.

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?

Explicitly says when to call it ('before multi-step workflows – opening LP positions, enabling automation, closing positions') and when you need specific data like contract addresses or strategy parameters. This gives the agent a clear trigger condition that maps onto the write_* workflow siblings.

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