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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so "Read-only." mostly restates structured data. The description does add useful context beyond annotations: the PKM Phase 3 provenance, the shape of each preset record, and the downstream consumption by create_typed_record.

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 verb and resource, followed by the usage pointer. The trailing "Read-only." is largely redundant against the readOnlyHint annotation, a minor waste but not enough to disrupt clarity.

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?

With no parameters and no output schema, the description must carry the return shape, and it does by naming key, label and field definitions. It omits any note about list size or ordering, but for a small static preset catalog that is a minor gap.

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, so the baseline is 4 and there is no parameter meaning the description needs to carry. Nothing in the description conflicts with the empty 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 and resource ("List the available typed-entity PRESETS") and enumerates exactly what each entry contains (key, label, field definitions with key/label/kind), plus a concrete example vertical. An agent can distinguish this from the many other *_list siblings without opening the schema.

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?

Explicitly routes the agent: "Use before create_typed_record to know which entity_type + fields exist," naming the alternative and the condition that selects this tool. It lacks an explicit when-not statement, but the prerequisite framing is clear and actionable.

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