analyze_dependencies

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

No annotations provided, so description bears full burden. It thoroughly explains behavior for Jira (user checks, hierarchy, sequenced plan) and Salesforce (record counts, relationships, owner checks, warnings, order). No contradictions.

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?

Well-structured with Jira and Salesforce sections plus usage note. All sentences add value; no redundancy. Front-loaded with primary purpose.

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?

No output schema, but description hints at outputs (plan, counts, warnings). Covers preconditions and behavior. Could be more explicit about return value format, but adequate given complexity.

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 covers all 3 parameters with descriptions (100% coverage). Description repeats basic parameter meaning but does not add significant additional context beyond schema. Baseline 3 appropriate.

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 clearly states the verb 'analyse', resource 'migration dependencies', and phase 'Phase 3'. It distinguishes from siblings by specifying its place in the workflow (after discover_schema, before build_artifacts) and provides platform-specific detail.

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 instructs to call after discover_schema and before build_artifacts. Advises on handling missing users. Lacks explicit alternatives or when-not-to-use, but context is clear given sibling tool names.

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