nexo_rules_migrate

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

The description discloses that the tool adds new rules and soft-deletes removed ones, but lacks details on whether it overwrites existing rules, requires a full rule set, or any side effects. No annotations are provided, so the description carries the burden but has gaps.

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 extremely concise, two sentences that directly state the purpose and key behavior, with no wasted words. Information is 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?

The description covers the core sync operation and effect, but for a mutation tool with side effects, it lacks details on return value, required JSON format, permissions, or reversibility. The presence of a dry_run parameter is noted but not explained further.

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 only parameter, dry_run, is fully described in the input schema with identical wording. The tool description adds no additional meaning beyond the schema, so baseline 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 'Sync' and the resource 'rules from JSON definition to database', and specifies the behavior 'Adds new, soft-deletes removed', effectively distinguishing it from sibling tools like nexo_rules_list.

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 usage when you have a JSON definition of rules to apply, but does not explicitly state when to use it versus alternatives (e.g., nexo_rules_list, nexo_rules_check) or provide any prerequisites or context.

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