vibemk_get_notification_rules

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

The description does not mention whether the operation is read-only or if it has side effects. Given the nature of listing, it is likely safe, but the lack of explicit transparency for a tool with no annotations means the agent must assume behavior.

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 brief and to the point, with no unnecessary fluff. The two phrases are concise, though the second phrase could be seen as slightly redundant.

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 simplicity of the tool (no parameters, no output schema specified), the description is adequate for basic understanding. However, the lack of any information about the output format or potential filtering options leaves some gaps in context.

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, which receives a baseline score of 4. There is no schema to clarify, and the description does not need to elaborate on parameter usage.

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 action ('List') and the resource ('notification rules'), which is specific and distinguishes it from other list tools. The additional phrase 'Show notification configuration' adds slight redundancy but does not detract from the clarity.

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 is provided on when to use this tool versus alternatives. While there is no direct sibling for listing notification rules, the description does not mention any specific scenarios or limitations, leaving the agent to infer usage.

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