unifier_rest_request

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

With no annotations, the description carries the full behavioral burden, and it does disclose a real constraint: write methods are gated behind an environment flag. It still omits auth/credential requirements, error and rate-limit behavior, and what happens to the request when the flag is absent, so the mutation profile is only partially visible.

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?

A single compact sentence with the method-permission rule front-loaded; nothing is padded. It is terse to the point of being cryptic (Spanish text amid English tooling) but every clause carries information.

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 deliberately open-ended REST proxy with nested/arbitrary objects, no output schema, and no annotations, the description is far too thin. It never explains the response shape, how to discover valid paths, or how the four parameters combine, leaving an agent largely guessing.

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 0% across four parameters, including a free-form 'body' and an arbitrary string map 'query', so the description must compensate and does not. It hints that 'path' must target a documented V1/V2 endpoint and that 'method' semantics differ by HTTP verb, but adds no format, encoding, or body-shape guidance.

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 ('Ejecuta un endpoint REST V1/V2 documentado'), so an agent knows this is a generic API passthrough rather than a domain action. It does not, however, differentiate itself from the many specialized siblings (unifier_list_shells, unifier_find_bp_record, etc.) that cover the same underlying API surface.

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 only usage rule given is the method gate (GET/HEAD free, writes need UNIFIER_ALLOW_WRITE=true). There is no guidance on when to reach for this generic escape hatch versus the 17 named Unifier tools, nor any prerequisite such as needing a documented endpoint path or credentials.

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