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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'READ-ONLY — only GET is allowed', so it does not contradict them. It also adds useful behavioral context: the response is parsed JSON. It omits auth requirements and rate-limit/error behavior, keeping it below a 5.

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?

Front-loads the purpose ('Power-user escape hatch'), then covers the constraint and the path format with examples. Every sentence earns its place, with only minor redundancy between the description and the schema's path example.

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 single freeform-path tool with no output schema, the description covers purpose, method restriction, path format, and return type (parsed JSON), which is sufficient to invoke correctly. Auth scope and error behavior are the only notable omissions, and there is no output schema to compensate for.

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 coverage is 100%, so the baseline is 3, but the description goes beyond the schema by stressing that the FULL path after the host must be passed including any query string, and supplies two concrete examples with different shapes. This clarifies the one freeform parameter meaningfully.

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?

States a specific verb and resource ('GET any OwnerRez API path') and explicitly positions itself as an escape hatch for paths 'not wrapped by a dedicated tool', which cleanly separates it from the many get_*/list_* siblings. An agent can tell immediately what this does and when it applies.

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 'not wrapped by a dedicated tool' clause gives a clear when-to-use condition and implicitly routes the agent to dedicated tools first, which is the key decision against ~25 siblings. It stops short of naming specific alternatives or stating exclusions/misuse cases, so it is strong but not fully explicit.

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