vk_get_migratio_6ce6501364d7

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

With no annotations provided, the description carries the full burden. It discloses the return semantics (whether migration was done), that a request body is usually not required, and that authentication is necessary. It does not mention response format, error conditions, or explicitly state read-only behavior, but for a simple status GET this is reasonably transparent.

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 five sentences covering purpose, endpoint, use case, request body, alias conventions, and auth. Each sentence adds value, though the alias sentence may be unnecessary given no parameters. It is efficient and front-loaded with the core 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?

For a simple no-parameter status check with no output schema, the description is fairly complete: it explains purpose, behavior, use case, request body expectation, and authentication. It stops short of explicitly stating the return type (e.g., boolean), but the phrase 'returns if...' implies it. It is adequate for the tool's 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?

The tool has 0 parameters (empty input schema), so the description cannot add much parameter-specific meaning. It does mention that path/query parameters are top-level and accept camelCase/snake_case aliases, but this is a generic note irrelevant to the current schema. Per the rubric, 0 parameters earns a baseline of 4.

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 tool 'gets migration status' and specifies the exact REST endpoint (GET /migration/wekan/status). It explains what it returns (whether the current user already performed the migration), which distinguishes it from migration mutation tools in the sibling list. The verb and resource are specific and 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?

It gives a concrete use case: showing a confirmation message when a user tries to repeat the same migration. It also notes authentication is required. However, it does not explicitly name alternative tools or say when not to use this tool, so it falls slightly short of full guidance.

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