sophos_accept_migration

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

No annotations are provided, so the description must disclose behavioral traits. It mentions 'completes the migration transfer' but fails to detail side effects (e.g., irreversible endpoint movement), authorization requirements, or synchronous/asynchronous 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 clear sentences with no redundant information. The purpose and prerequisites are front-loaded.

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 exists, and the description does not mention what the tool returns (e.g., status, job ID). Also lacks detail on optional parameter 'endpoint_ids' for accepting a subset. Agent cannot infer the full effect or response format.

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 parameters are already documented. The description does not add meaning beyond the schema beyond contextualizing 'token' and 'tenant_id' as from sending and receiving tenants respectively, which is baseline.

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 the action ('Accept'), the resource ('endpoint migration job'), and the context ('receiving tenant' using 'job token' from 'sending tenant'). This distinguishes it from siblings like sophos_start_migration which initiates migration.

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?

The description implies a prerequisite (job token generated by sending tenant) but does not explicitly state when to use this tool versus alternatives like sophos_get_migration_job or sophos_list_endpoint_migrations. No explicit when-not or alternative guidance.

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