Delete AWS AgentCore Memory Resource

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description's 'Permanently delete' reinforces the destructive nature but adds limited new behavioral context. It does clarify the target ('for a credential') and emphasizes irreversibility, but it does not disclose additional traits like specific side effects or authorization requirements.

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 a single, clear sentence that conveys all necessary information without waste. It is front-loaded and efficient, earning a high score for conciseness and structure.

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 simple tool with one parameter and no output schema, the description combined with annotations provides sufficient context for an agent to invoke it. It covers the destructive, idempotent nature and the target. However, it does not specify behavior when the resource doesn't exist or whether the credential must still be valid, which would improve completeness.

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 coverage is 100% and the parameter 'credential_id' is described as 'The AWS AgentCore credential id'. The description adds minimal meaning beyond this, just clarifying that it is the credential whose memory resource gets deleted. Since the schema already documents the parameter fully, the baseline of 3 is appropriate.

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 clearly states the action: 'Permanently delete the AWS AgentCore memory resource for a credential.' It specifies the verb (delete), the resource (AWS AgentCore memory resource), and the scope (for a credential), which distinguishes it from siblings like lyzr_memory_delete (general memory deletion) and lyzr_credential_delete (credential deletion).

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 tool's purpose is implied by the name and description, but there is no explicit guidance on when to use it versus alternatives, such as checking resource status first or using a different deletion tool. It does not clarify when not to use it or mention prerequisites like ensuring the credential no longer needs the memory resource.

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