get_rules

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

With no annotations supplied, the description carries the full disclosure burden, and it discloses almost nothing behavioral. It does not say whether the call is read-only, what happens if no rules exist, whether the result is the full ruleset or a summary, or anything about size/format of the response.

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 short imperative sentence, front-loaded with the action and with no filler. It is not padded, though its brevity contributes to the specification gaps noted elsewhere rather than being a model of efficient completeness.

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 zero-parameter getter with no output schema, the description is the only place return behavior can be described, and it omits it. It is minimally sufficient to know roughly what the tool does, but an agent cannot predict what it will receive back or how to use it.

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 and the schema is an empty object, so there is no parameter meaning for the description to add. Baseline for a parameterless tool applies, with no misdirection in the description.

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?

"Reread the rules for working with your human" pairs a specific verb (reread) with an identifiable resource (a stored ruleset), so an agent can guess it returns previously-supplied guidance. However, "the rules" is never defined — where they come from, what they cover, or whether the tool returns text or structured items — leaving the purpose only partially pinned down against siblings like get_profile and remember.

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 imperative "Reread" hints at a habit but gives no condition for when it should be invoked versus get_profile, get_map, or remember. There are no exclusions and no statement of prerequisites (e.g., whether rules must have been set previously), so selection is left entirely to inference.

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