ck_deployment_advisor

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

Discloses that analyze and dns_guide are read-only, generate_files is a write operation (creates files). Mentions dry_run to preview writes. Annotations (readOnlyHint=false) are consistent; description adds detail beyond them.

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?

Four concise sentences: main purpose, mode summary, required parameter note, usage guidance. Front-loaded and efficient with no extraneous content.

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 all modes, their behaviors, and expected outcomes (recommendations, file generation, DNS instructions). With output schema present, no further return details needed. Complete for a multi-mode 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?

Adds meaning beyond schema: explains dry_run purpose ('preview what would be created without writing files') and when to use it (with generate_files). Clarifies project_root is required.

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?

Description states specific verb-resource pairs for three modes: analyze (analyze stack), generate_files (generate configs), dns_guide (return DNS instructions). Clearly distinguishes from sibling tool ck_budget.

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 when to use: 'before deploying a new project or when setting up CI/CD for the first time'. Recommends alternative 'ck_budget' for cost checks. Also describes mode-specific usage.

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