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

Annotations cover the safety profile (non-read-only, non-destructive, non-idempotent, closed-world), so the bar is lower. The description adds real context beyond them: the description field becomes the first message (a side effect), and the operation is restricted to members (an auth requirement). It does not describe the returned object, though no output schema exists.

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 in the first clause and every sentence carries content (definition, lifecycle, member restriction, usage rule). It is slightly long and the 'take shape later' phrasing is a touch indirect, but nothing is filler.

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 non-idempotent creation tool with full schema coverage, no output schema, and annotations already declaring the safety profile, the description supplies the remaining essentials: what the entity is, what gets created as a side effect, who may call it, and how the lifecycle continues into attached missions/resources.

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 100%, so the baseline is 3, but the description earns extra credit by explaining the semantic role of the `description` parameter ('becomes the first message ... can be written in plain words') — meaning the schema itself does not convey. It does not clarify `name` beyond the schema's own example.

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 concrete verb+resource ('Start a process in a rikma') and then defines what a process actually is ('a named thread with its own conversation'). It explicitly distinguishes it from the siblings it could be confused with — 'something that is not yet a mission or a resource' — so an agent can separate it from prepareMissionTool/createTaskTool/createProjectTool.

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 explicit when-to-use ('when the user wants to record something the rikma is pursuing') and an explicit exclusion ('not to file your own notes'), plus a prerequisite constraint ('Members only'). It also routes the later-stage workflow to the named sibling attachToProcess, so alternatives are covered.

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