amplify_preflight

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

No annotations, so description carries full burden. Discloses that it queries stored lessons/decisions and returns structured output. Implies read-only but doesn't explicitly state idempotency or side effects. Good but not exhaustive.

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?

Very concise: two sentences plus a brief call to action. Version number is front-loaded. No wasted words.

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?

Describes return fields (risk_level, matched patterns, etc.) despite no output schema. Covers all 4 parameters. Could explicitly state idempotency or read-only nature, but overall sufficient for a preflight check tool.

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%, so baseline is 3. Description adds value by noting alias for 'prompt' ('task') and clarifying 'context' parameter as optional extra info. Slightly improves understanding beyond 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?

Clear verb ('check') + resource ('stored lessons + decisions') and outcome ('Returns risk_level...'). Distinguishes from sibling tools by focusing on preflight checks before task execution.

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 states 'Call this BEFORE diving in when working on something that touches a familiar area.' Provides strong when-to-use guidance. Lacks explicit when-not-to-use, but context implies use for familiar areas where failure patterns exist.

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