rest_query

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

No annotations exist. The description says 'mutate' but does not disclose destructive behavior (DELETE), authorization needs (key_type in schema), rate limits, or side effects. The schema parameter descriptions help slightly, but overall transparency is low.

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?

Two sentences, front-loaded with purpose, then methods. No waste; every sentence contributes meaning.

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?

Complex tool with 6 parameters (including nested object) and no output schema. Description fails to mention return format, pagination, error handling, or how results are structured. Incomplete for an AI agent to reliably invoke.

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% with detailed parameter descriptions. The tool description adds high-level context ('Query or mutate data') but does not further explain parameters beyond what the schema provides, so baseline 3 is appropriate.

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 clearly states the tool makes REST API queries/mutations ('Query or mutate data via the PostgREST REST API'). It distinguishes from siblings like run_sql by specifying the REST interface.

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 mentions supported methods (GET/POST/PATCH/DELETE) which implies usage, but lacks explicit when-to-use or alternatives (e.g., run_sql for SQL). No exclusions or prerequisites provided.

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