pentest_rules

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

No annotations are supplied, so the description carries the full burden; it does disclose that the response is the plugin's own policy of what it will and will not do, which is meaningful behavioral context. However, it says nothing about whether the call is side-effect free, whether output is static across a session, or the format/shape of the rules. For a read-only zero-argument tool this is a moderate gap rather than a severe one.

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?

A single sentence with the key noun phrase front-loaded and a parenthetical that adds real meaning rather than padding. Nothing is redundant or restated from the name.

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?

With no parameters, no annotations and no output schema, the description is nearly sufficient; it conveys the concept of the returned value. A slight gap remains because the concrete shape of the returned rules (list, text block, field names) is left entirely unstated.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description correctly does not invent inputs.

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 specific verb ('Return') and resource ('currently enforced rules of engagement'), and the parenthetical clarifies the semantics as a capability/exclusion policy. It is distinguishable from every listed sibling (scan, lookup, export, status tools), though it does not explicitly name a contrast.

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 explicit when-to-use or when-not statement, nor any reference to calling it before scans. Usage is only implied by the phrase 'currently enforced', which hints that it reflects live policy state. An agent must infer the natural workflow (check rules before acting) on its own.

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