sophos_get_migration_job

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

With no annotations, the description bears full transparency burden. It clearly indicates a read operation to fetch status and details, implying no side effects. However, it does not mention permissions or rate limits, which are minor omissions for a simple GET.

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 description is a single, well-structured sentence that is appropriately concise. It front-loads the verb and resource, with no superfluous information.

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?

Given the tool's simplicity (GET with two parameters), the description adequately covers the purpose and parameters. However, the absence of an output schema means the agent must infer the return structure from context, which is a minor gap.

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%, and the schema descriptions ('Tenant UUID', 'Migration job ID') are clear. The tool description adds no additional parameter details beyond what the schema provides, so a 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 'Get the status and details of a specific endpoint migration job,' using a specific verb and resource. It distinguishes from sibling tools like 'sophos_start_migration' (starts a job) and 'sophos_list_endpoint_migrations' (lists jobs), making the purpose unambiguous.

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 lacks guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., valid tenant_id, migration_job_id) or imply when it should be used instead of other migration-related tools.

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