Forbidden Guard — restricted terms + lexical rules (LEX-002/003), payload inlined

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is clear. The description adds specific behavioral context: it returns records with inlined content (v7 payload contract) and focuses on restricted terms/lexical rules, which is useful but not critical beyond annotations.

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 wasted words, though the first sentence repeats the title. Still concise and front-loaded with key information.

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 read-only preset tool with a single parameter and no output schema, the description adequately states what records are returned and their content type. Missing details like pagination or ordering are acceptable given the simplicity and annotations.

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% with one boolean parameter 'inline' already described as 'false → metadata-only (legacy v6 shape)'. The description does not add any extra meaning or usage guidance for this parameter, so baseline of 3 is appropriate.

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 explicitly states the tool returns records with inlined content for restricted terms and lexical rules (LEX-002/003), and uses a distinctive name 'Forbidden Guard' that sets it apart from sibling preset tools (e.g., gkb_preset_ilg, gkb_preset_quality). This provides clear verb+resource+scope differentiation.

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?

No guidance on when to use this tool versus alternatives. The description simply states what it does without explaining scenarios where it should be preferred over sibling tools like gkb_preset_topical or gkb_preset_tech.

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