grimoire_context

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

No annotations are provided, so the description bears full burden. It indicates a read-only operation returning data, but does not mention any prerequisites, side effects, or required permissions. For a simple context retrieval, this is adequate but not comprehensive.

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 with no extraneous words. The first sentence lists what is returned, and the second gives clear usage direction. Perfectly front-loaded and efficient.

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?

Given no parameters and no output schema, the description fully covers what the tool does and how to use it. It explains the content and importance of reading it first, which is sufficient for a zero-parameter context tool.

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?

The tool has zero parameters, so the schema provides no information. The description adds significant value by detailing the contents of the returned context (targets, interfaces, hardware, etc.), meeting the baseline of 4 and exceeding it with rich output description.

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 clearly states the tool returns engagement context for the assessment, listing specific items (operator-declared targets/IPs, interfaces, hardware, parameters, host-detected devices). This distinctly sets it apart from sibling tools like grimoire_search or grimoire_env.

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?

The description explicitly instructs to 'Read this first and tailor every step and command to the actual targets and hardware in scope,' providing clear when-to-use context. It does not list exclusions or alternatives, but the sibling list implies this is the primary context retrieval tool.

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