rlm_delete_summary

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

No annotations and the description does not disclose important behavioral traits like reversibility, permissions, or the effect of partial parameter specification.

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?

Extremely concise (3 words) but sacrifices completeness; a balanced sentence would have added parameter context without losing conciseness.

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 tool with two optional parameters, the description fails to provide enough context for correct use, such as what happens if no parameter is provided.

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% and the description completely omits parameter semantics; no explanation of summary_id vs. document_path, their interplay, or defaults when both are omitted.

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 'Delete stored summaries.' clearly states the verb (delete) and the resource (stored summaries), distinguishing it from siblings like rlm_store_summary (store) and rlm_get_summaries (get).

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 on when to use this tool vs. alternatives, no prerequisites, and no clarification on parameter selection or exclusivity.

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