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

Annotations provide only readOnlyHint, and the description adds real context: it is an escape hatch, only GET is permitted, the path must include the query string, and it returns parsed JSON. It does not mention auth requirements, pagination, or rate limits, but the safety and method constraints are well disclosed.

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?

Three tight sentences, front-loaded with the escape-hatch framing and constraint, then the calling convention, then the return type. No filler.

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-parameter raw-read tool with no output schema, the description covers the calling convention, method constraint, and return shape (parsed JSON). Auth handling and pagination behavior of arbitrary endpoints are unaddressed, which is a minor gap given the tool's generic nature.

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% and already shows a path example, but the description adds value by stressing the FULL path after the host, the leading slash, and that the query string must be embedded in the path, with two concrete examples including a resource-by-id path.

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 (GET) and resource (any OwnerRez API path), and explicitly positions itself relative to the other tools as the 'escape hatch' for paths 'not wrapped by a dedicated tool'. An agent can distinguish it from get_booking/list_properties without opening schemas.

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?

Clearly frames when to use it: only for API paths that dedicated tools don't cover, implying dedicated tools should be preferred when they exist. It does not name specific siblings as alternatives, but the routing condition is stated plainly.

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