rms_wiki_pack

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

With no annotations, the description carries the full burden. It usefully signals that the output is 'material for an agent' drawn from 'verified sources' (implying a read/generate operation rather than a destructive one), but it never says whether anything is written to disk, how expensive the operation is, or that refresh_code can force a reindex.

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, zero waste, with the core action front-loaded and the return-value note immediately after. Nothing is redundant or buried.

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?

The description partially covers the missing output schema by stating the tool 'returns material' for documentation, but it does not describe the shape of that material or what happens with all-optional parameters. With no annotations and no output schema, a generation tool of this kind warrants a bit more disclosure.

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 100%, so all three parameters (project, manifest, refresh_code) are already documented in the schema. The description adds no extra meaning such as default behavior when 'project' is omitted or what a custom manifest section can contain, so the baseline of 3 applies.

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?

The description gives a specific verb ('Generate') and resource ('wiki context pack') and names its two inputs (vault and code index), so it is clearly distinct from search/read/write siblings. It stops short of naming a sibling tool it might be confused with, which keeps it out of the top band.

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?

Usage is only implied: an agent can infer this is the tool to reach for when it needs source material to author wiki documentation. There is no explicit when-to-use/when-not statement, no mention of prerequisites, and no pointer to alternatives such as rms_overview or rms_search for related retrieval.

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