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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the safety profile is covered. The description adds useful context beyond that: it discloses the returned payload (rows, keys, status, version, recent changes) and the version-freshness motivation for calling it.

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?

Purpose is front-loaded, but the single sentence is dense and includes noise like the awkward parenthetical "(also from the site)" and an external docs URL. The core guidance survives, but the prose could be trimmed without loss.

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 output schema, the description carries the burden of describing returns and does so (rows, keys, status, version, recent changes), which is the key missing piece for a read tool. The only residual gap is the undocumented sessionId parameter and the unclear relationship to other read siblings.

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 50%: kind has an enum with a short description, while sessionId is undocumented. The description partially compensates by naming the kind values (rikma blueprint, profile, wish) and implying "latest session" semantics, but sessionId remains unexplained in both schema and description, so this sits at the baseline.

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 ("Read the person's current draft list on 1lev1") and enumerates the three kinds (rikma, profile, wish), which distinguishes it from write-oriented siblings like setAssistantItemsTool. It does not, however, clarify how it differs from getWishDetailsTool or listRikmaProcessesTool, so it falls short of full sibling differentiation.

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 gives a when-to-use condition with an alternative: "Call it before setAssistantItems when you are not sure you have the latest version." That is actionable routing guidance, though it covers only one sibling and offers no when-not guidance.

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