alterios_rest_write

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

No annotations provided; description only says 'mutating' and 'requires write gates'. Doesn't disclose dry-run behavior, destructive consequences, or authentication needs, leaving significant gaps.

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 and a key requirement. Every sentence is essential and no fluff.

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 8 parameters, 3 required, and an output schema, the description is too minimal. Doesn't cover usage patterns, parameter relationships, or output format. Incomplete for a complex tool.

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%, yet the description adds no parameter-specific meaning. Does not explain body, method, path, or safety flags like allow_destructive or dry_run.

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?

Description clearly states 'mutating REST request', distinguishing from read-only siblings like alterios_rest_get. Mentions 'write gates', adding specificity.

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?

'Execution requires explicit write gates' gives a clear prerequisite but no exclusions or comparisons to similar tools like alterios_call_write_service. Lacks guidance on when not to use.

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