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

The annotations already declare readOnlyHint, destructiveHint false, and openWorldHint false, so the safety profile is covered. The description adds that results come from REBASE methylation-sensitivity tables localised onto the user's sites, which is useful provenance, but it does not explain edge cases or assumptions beyond that.

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 tight sentence with no filler, and the core concept is front-loaded. Its grammar is slightly awkward as a question fragment, but it remains efficient and readable.

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 read-only tool with annotations, a 100%-covered schema, and an output schema, the description supplies the essential purpose and data source. It is somewhat terse about how the plasmid subject is used, but that is documented in the schema, so nothing critical is missing.

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 description coverage is 100%, so the schema already documents all three parameters, including the enzyme list and subject reference. The description adds contextual meaning with 'given enzymes' and 'ON THIS PLASMID', but no parameter-specific semantics beyond what the schema provides.

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 states a specific computation: checking whether host methylation blocks named enzymes on the current plasmid, using REBASE methylation-sensitivity data. It is distinguishable from generic restriction-site tools by the methylation-block question, though it does not explicitly name a sibling alternative.

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 phrase 'ON THIS PLASMID' and 'given enzymes' implies the usage context, but there is no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives such as restriction-site finding or digest simulation, leaving the agent to infer when this check is appropriate.

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