get_rules

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

With no annotations, the description carries the full burden. The verb 'Get' and the word 'current' imply a read-only, point-in-time query, and the parenthetical clarifies scope, but no additional behavioral traits are disclosed such as side-effect guarantees, failure behavior, or output format. It is minimally transparent but not rich.

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, front-loaded sentence with no filler. The parenthetical examples add useful specificity without bloating the text, and every word contributes to understanding the tool's purpose.

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 simple one-parameter, zero-required tool this is mostly adequate, but there is no output schema and no usage guidance, so the agent is left to guess the return structure and when to prefer this over comparable tools. The examples partially compensate but do not fully cover the missing 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?

Schema description coverage is 100%, and the only parameter, 'address', is already well documented as 'Optional host:port to query instead of the project server'. The description adds no additional parameter meaning, so the baseline score of 3 applies.

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 states a specific verb ('Get') and resource ('current server rules') with concrete examples ('gravity, weather, version'), so the agent can tell what the tool acts on. It does not explicitly differentiate from close siblings like get_status or get_server_diagnostics, so it misses the extra point for sibling distinction.

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 gives no guidance on when to use this tool versus alternatives such as get_status or get_server_diagnostics, and it states no prerequisites or exclusions. It merely states what it does, which is insufficient for choosing among the many sibling tools.

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