rest_query

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

The description only says 'Query or mutate data' with no disclosure of behavioral traits such as authentication requirements, rate limits, or potential side effects of write operations (POST/PATCH/DELETE). Given no annotations, the description fails to adequately convey the tool's impact.

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 a single sentence that is concise and front-loaded with purpose. However, it could be structured with bullet points for clarity, but it is still efficient with no wasted words.

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 6 parameters, no output schema, and no annotations, the description is incomplete. It does not clarify response format, error handling, or how to structure the body for POST/PATCH. The agent lacks critical context to use the tool safely and effectively.

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% with each parameter described in the input schema. The description adds no additional meaning beyond restating HTTP methods. Baseline 3 is appropriate as the schema does the heavy lifting.

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's function: 'Query or mutate data via the PostgREST REST API' and lists supported HTTP methods (GET/POST/PATCH/DELETE). It distinguishes itself from sibling tools which are specific operations, making its purpose unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives like 'run_sql' or other query tools. The description lacks explicit context for when-not or which method to choose, leaving the agent without sufficient decision criteria.

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