validate_strategy

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

Without annotations, description discloses static analysis nature, non-execution, and checks for hooks and forbidden patterns. Lacks mention of side effects or output 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 concise sentences with key information front-loaded. Every sentence adds value without 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?

Covers purpose, checks, and usage timing. Lacks description of return value (e.g., pass/fail or detailed report), which is relevant given no output schema.

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 single parameter 'code' is fully described in schema. Description adds meaning by explaining what the code is checked for (hooks, forbidden patterns), going beyond the schema's 'Python source' description.

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 a static-analysis check on Python FLOX strategy, specifying AST parsing, expected hooks, and forbidden patterns. It distinguishes from sibling tools like validate_strategy_no_lookahead by focusing on general code safety.

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 recommends use before running user-authored code and states it does not execute. Does not explicitly mention when not to use or provide alternatives, but context from sibling tools allows inference.

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