rem_delete

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

With no annotations, the description carries full burden for behavioral disclosure. It only says 'Delete entity,' which implies mutation but does not explain cascading behavior (despite the cascade parameter), permanence, side effects on related data, or any authorization requirements. Significant behavioral gaps exist.

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 extremely brief (two words), which is concise in length but under-specified. It is not front-loaded with important information because there is no information. This is not effective conciseness; it is an absence of content, similar to the 'Process' example.

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 delete operation with 4 parameters, a complex type enum, and no output schema, the description is severely incomplete. It fails to explain return values, error handling, cascading alternatives, or how the operation affects project data. An agent cannot safely call this tool based on the given description.

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%, so the description must compensate for parameter meaning, but it provides nothing about oid, type, cascade, or project_id. The schema itself lists parameter names/types but no descriptions; the description adds zero semantic value. This is a critical gap for a delete operation.

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 a clear action (delete) but the resource is vague ('entity'). It does not specify what kinds of entities can be deleted, nor does it differentiate from siblings like rem_update or rem_get beyond the obvious deletion action. This is a generic but not tautological purpose.

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 about when to use this tool versus alternatives such as rem_update or rem_get. There are no conditions, prerequisites, or exclusions mentioned. The description gives no context to help an agent decide when deletion is appropriate.

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