sophos_list_endpoint_migrations

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

No annotations are provided, so the description carries the full burden. It only states 'List endpoint migration jobs' and 'Shows status', without disclosing pagination (though page_size parameter exists), idempotency, or any side effects. More behavioral context is needed.

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 concise sentences with no wasted words. The key action and resource are front-loaded: 'List endpoint migration jobs for a tenant.'

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?

For a simple list tool with 3 parameters fully described in the schema, the description is mostly sufficient. However, lacking an output schema, it could provide more context on the return structure or the concept of 'migration jobs'. Still, it's reasonably complete for its simplicity.

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% with descriptions for all three parameters. The description adds no additional meaning beyond the schema, e.g., it doesn't explain the 'mode' enum values or clarify pagination behavior. Baseline score of 3 is 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?

The description clearly states the verb 'list', the resource 'endpoint migration jobs', and the scope 'for a tenant'. It distinguishes itself from siblings like sophos_get_migration_job (which gets a single job) and sophos_list_migration_endpoints (which lists endpoints within a 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?

No explicit guidance on when to use this tool over alternatives such as sophos_get_migration_job or sophos_list_migration_endpoints. The description implies it's for listing all migration jobs but does not provide context for selection.

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