rules_manager

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

No annotations are provided, so the description carries the full burden. It mentions read and save/update actions but does not disclose side effects of saving (e.g., overwriting existing rules), required permissions, or any consequences of the operations. This leaves significant behavioral ambiguity for an agent.

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 a single, well-structured sentence that front-loads the purpose ('Manage project rules') and then uses a colon to specify the two modes. Every word contributes value, with no redundancy or unnecessary detail.

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 the tool's simplicity and 100% schema coverage, the description provides the core purpose and operation modes. However, it lacks explicit usage guidance and behavioral details (like content being required for save), leaving the agent to infer some important context that is only partially available in the schema.

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 schema covers both parameters with descriptions, so baseline is 3. The description adds meaning by explaining that 'get' corresponds to 'read current rules' and 'save' to 'save/update rules', which clarifies the purpose of the action enum beyond the schema's generic 'The rules action to perform'.

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 manages project rules, specifying two specific actions: reading current rules and saving/updating rules. This distinguishes it from sibling tools like task_manager and plan_manager, which handle different resources.

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 implies this tool is for managing rules, but it does not explicitly state when to use it over alternatives or provide any exclusions. The context is clear from the resource name, but no direct guidance is given about choosing between get and save actions or comparing to sibling managers.

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