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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the read-only safety profile is covered. The description adds that entries are non-persistent starters which adopt via ledger_metric_starters_adopt, but says nothing about output shape or response structure.

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?

Front-loads what the tool returns, then the usage trigger, then the adopt workflow. Slightly dense in the closing 'pick/describe/offer' instruction, but every clause carries actionable information.

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 no-param read tool with no output schema, the description tells the agent what the trees contain (metric levels, links) and how to act on the result including the adopt hand-off. Missing only a hint of how large/varied the starter catalog is.

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?

Zero parameters, so the baseline is 4; there is nothing for the schema to document and nothing for the description to compensate for. It correctly does not fabricate parameters.

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-resource (starter metric trees by business shape) and screens off the likely-confused sibling ledger_metric_presets_list. An agent knows exactly what comes back: trees of metrics with levels and links.

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?

Explicit trigger: 'Reach for this before ledger_metric_presets_list when a workspace has no metrics yet or asks how its numbers fit together.' It names the alternative, the ordering, and the qualifying condition — nothing left to inference.

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