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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description usefully adds two behavioral facts beyond the annotations: input format is sniffed rather than declared, and Newick conversion is lossy for annotations carried by richer formats.

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 sentences, front-loaded with the core action and formats before the rationale. Tight overall, though the second sentence carries two ideas (lossiness plus why conversion is explicit) that could be trimmed.

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?

An output schema exists so return values need not be explained, and annotations cover the safety profile. The description supplies the remaining non-obvious context an agent needs: format handling and lossiness caveat.

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 tree, format, name, and the nested _subject/_files objects; the baseline of 3 applies. The description adds only the format-sniffing note, which lightly informs the tree param but does not elaborate on any parameter beyond the schema.

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?

States a specific verb (convert) and resource (tree) and enumerates the four formats (Newick, NEXUS, PhyloXML, NeXML), which is more than a restatement of the title. However, it does not distinguish itself from the closely related sibling transform_tree, leaving the agent to infer the boundary from names alone.

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 closing clause explains why conversion is a deliberate user-chosen step rather than silent export behavior, which implies the intended use context. It stops short of explicit when-to-use/when-not guidance or naming an alternative such as transform_tree or build_tree.

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