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

Annotations declare it is not read-only and not destructive, so the write nature is known. The description adds meaningful context that this seeds from 'what is on it now' and returns rows with keys, which annotations don't convey. But it does not state whether starting overwrites existing list contents, whether it can be called repeatedly, or the auth/ownership requirements.

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?

Dense but front-loaded: the core purpose opens the sentence, then branches into (a) and (b), then the follow-up flow. Some nested parentheticals make it slightly heavy, but no sentence is wasted.

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?

Covers both usage branches, the follow-up editing/saving workflow, an exclusion to a sibling tool, and a docs link. Given the complex multi-step domain and no output schema, it provides an agent enough to call correctly, though it omits return-shape detail and ownership/permission context.

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 coverage is 0%, so the description must compensate. It explains that text is 'what they told you' and ratsonId comes from listMyWishesTool, and that kind selects profile vs wish. However it never maps ratsonId is only for wish, nor clarifies that text can seed either kind, leaving some ambiguity about parameter combinations.

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: 'Open the person's living list' of a PROFILE or WISH, with the two kinds clearly distinguished. It does not name what a 'living list' or 'rikma' means in domain terms, but the two branch types are concrete enough for an agent to act.

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?

Gives clear when-to-use guidance for each branch (pass text vs ratsonId) and names the follow-up tools (setAssistantItems, reviseAssistant, applyAssistant). It also states an exclusion: 'A rikma is not started here: use proposeRikmaBlueprint.' Lacks explicit preconditions (e.g., must a profile already exist to seed from?).

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