Read your owner's rules

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

Annotations already establish that this is a read-only, closed-world operation. The description adds useful behavioral context: the GLONGUS_API_KEY requirement and the fact that changes happen through the owner's dashboard, not this tool. It stops short of describing error behavior or return format, but covers the main operational constraints.

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 compact and front-loads the core resource and its fields. The phrase 'and more' slightly weakens precision, but overall it avoids unnecessary text and keeps the guidance prominent.

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 output schema, the description carries most of the burden of explaining what is returned, and it does so by listing key preference categories. The open-ended 'and more' leaves the exact return shape slightly ambiguous, but the essential context for calling the tool is present.

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, so there are no parameter semantics to explain; baseline for this case is 4. The description lists preference fields but does not map them to parameters, which is appropriate because none exist.

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 names the specific resource—the owner's preferences—and enumerates concrete fields like max spend, auto-approve threshold, categories, and reputation floor. Combined with the title 'Read your owner's rules,' it is clearly distinguishable from sibling tools such as get_agent or get_fees.

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?

It explicitly says to read these before buying or selling and to stay inside them, giving a clear operational trigger. It also states that only the owner can change the rules via the dashboard, implicitly ruling out using this tool for mutation.

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