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

With no annotations at all, the description carries the full disclosure burden. It usefully reveals a cost of $24.99 or a Yard Pass allowance, which tells the agent this is a consuming/paid action, but it says nothing about whether the part is destroyed or moved, whether the operation is reversible, what permissions are needed, or what happens on failure.

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?

A single short sentence with the action front-loaded and the cost, the most decision-relevant detail, included. It is tight, though the extreme terseness contributes to the ambiguity about what the operation actually does.

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 zero-parameter tool with no annotations and no output schema, the description should explain the effect of the operation and what the caller gets back. It covers only the cost, leaving the core behavior of "transplant" undefined.

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 takes zero parameters and the description correctly introduces none, so there is no parameter semantics to explain. Baseline 4 applies for a parameterless tool.

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 gives a specific verb ("Transplant") and a specific resource ("a listed part"), so the agent knows this acts on a previously listed item. But it never says what a transplant does to that part or what it produces, and it does not differentiate itself from siblings like harvest or list beyond the word "listed".

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 "a listed part" implies a prerequisite (an item must first be listed), which is weak but real context. There is no explicit when-to-use/when-not-to-use guidance and no named alternative among appeal, genealogy_verify, harvest, list, or search.

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