assess_migration_readiness

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about whether the assessment is read-only or mutating, whether it requires external system access, how expensive or slow it is, or how results are produced. It does at least imply the output is scored guidance for a migration, but that is inference rather than disclosure.

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?

The one-line purpose statement is front-loaded, and the Args block is compact and scannable. The docstring framing ('Args:') is slightly machine-y but every line carries information; nothing is wasted.

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?

An output schema exists, so return values need not be explained, and all parameters are covered. However, for a five-parameter assessment tool with no annotations, the description omits the behavioral envelope — cost, prerequisites, and what makes an assessment meaningful — leaving an agent able to call it correctly but without expectations about the call.

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 description coverage is 0%, so the description must compensate, and it largely does: every one of the five parameters is documented with meaning, and concrete examples are given for source_platform ('Legacy CRM', 'Argus Safety', 'Veeva Vault') and area ('crm', 'safety-pv', 'regulated-content', default 'crm'). It does not state units or plausible ranges for country_count/user_count, or the accepted module name vocabulary, leaving some ambiguity.

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 — 'Run a migration readiness assessment' — scoped to 'any commercialization area', which is a clear action an agent can distinguish from sibling read/lookup tools. It stops short of naming which sibling (e.g. plan_multi_country_rollout, plan_system_validation) to prefer under which conditions.

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?

No guidance on when to call this versus plan_multi_country_rollout, plan_system_validation, or run_validation, all of which sit adjacent in the workflow. The only hint is that it applies to 'any commercialization area', which implies breadth but not selection criteria or prerequisites.

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