Load coding context from DevVault

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

No annotations are present, so the description carries the transparency burden. It discloses retrieval behavior, the quality consequence of long queries, the precedence of explicit collections over inference, and the empty-result handling. It does not explicitly state that the operation is read-only, though 'returns' and 'load' strongly imply 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?

The description is dense but not padded; every sentence carries an actionable instruction. The key imperative 'Call this BEFORE writing any code' is front-loaded, and the rest of the guidance earns its place.

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?

Despite having no output schema, the description explains the high-level return payload: rules/conventions plus a list of deeper references. It also covers the no-results edge case with explicit instructions on how to behave. This is sufficient for an agent to invoke and interpret the tool correctly.

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%, setting a baseline of 3. The description adds meaningful semantics: task should be one short sentence, full prompts retrieve badly, collection should be used when the user names it with @, and an explicit name always wins over inference. This goes beyond the schema's field descriptions.

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 action and resource: it loads the user's own coding rules and conventions for the current area, plus a list of deeper reference material. This clearly separates it from the sibling search/write/list/save tools by focusing on loading personal coding context.

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 guidance: call before writing any code, and call again whenever the work area changes. It also gives clear constraints: pass a one-sentence task, do not paste the full prompt, and pass an explicitly named collection. It does not name an alternative sibling such as devvault_search, so the 'vs alternatives' part is not fully explicit.

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