Raw Appsmith API call

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

With no annotations provided, the description carries the full burden. It does disclose a critical safety behavior (destructive methods require an env var), which is genuinely valuable. However, it doesn't disclose what happens on error, whether responses are parsed, auth requirements, or rate limits. It also doesn't discuss the scope of 'any endpoint' - e.g., whether it can reach non-Appsmith endpoints or is limited to the Appsmith API. The destructive-method gate adds meaningful context beyond the schema.

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 the primary purpose, then the critical constraint. Zero wasted words. Every sentence earns its place - the first defines what it does and when, the second discloses the destructive-method gate. Efficient and clear.

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 generic REST-call tool with no output schema and no annotations, the description sets expectations reasonably well. It covers purpose, when to use, and the key safety gate. Given that this is a deliberately raw/escape-hatch tool, describing the full universe of possible behaviors might be counterproductive, but it could mention error handling or response format. The description is adequate given the tool's intentionally 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 description coverage is 100%, so all 4 parameters have descriptions in the schema (method, path, body, query). The description doesn't add parameter detail beyond the schema, but with full coverage the baseline is 3. The description adds nothing about formatting of body/query beyond what the schema states, so it doesn't elevate above baseline.

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 states it 'Calls any Appsmith REST endpoint directly, for things the typed tools do not cover.' This clearly states the verb+resource (calls Appsmith REST endpoints) and positions it as a raw/escape-hatch alternative to typed tools. It distinguishes its purpose from siblings (which are typed tools covering specific endpoints), though it doesn't enumerate which specific endpoints it covers beyond the generic capability.

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 explicitly says this is for 'things the typed tools do not cover', giving clear context on when to use it vs alternatives. It also states the important behavioral rule: 'GET is always allowed; other methods require APPSMITH_MCP_ALLOW_DESTRUCTIVE=true.' This is explicit usage guidance including a precondition/constraint.

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