Get AWS AgentCore Provisioning Status

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

The description aligns with the readOnlyHint, openWorldHint, and idempotentHint annotations but adds no additional behavioral context beyond restating the tool's purpose. No details are given about polling behavior, status values, or what the response contains.

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, front-loaded sentence with no unnecessary details. Every word adds value, making it highly concise and well-structured.

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?

The tool is simple with one parameter and strong annotations, but the absence of an output schema means the description should explain what status information is returned. It does not, leaving the agent unsure of the response format or possible provisioning states.

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?

The input schema has 100% coverage for the single required 'credential_id' parameter, with a clear description. The tool description does not add extra parameter context, but the schema already fully documents the parameter, so the baseline 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 uses a specific verb ('Get') and a precise resource ('provisioning status of an AWS AgentCore memory resource'), clearly distinguishing it from sibling status tools like mem0_status and supermemory_status by naming the provider and resource type.

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 description implies this tool is for retrieving provisioning status, but provides no explicit guidance on when to use it versus validating, provisioning, or listing resources. Usage context is only inferred from the tool name and sibling tools, with no stated prerequisites or alternatives.

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