edb_get_memory_region_info

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint, making the safety profile clear. The description adds that it only shows regions defined with edb_set_memory_permissions, which is a useful scope clarification but not extensive behavioral disclosure beyond annotations.

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?

Three sentences front-loaded with core purpose, then an analogy, then return type. No wasted words; every sentence adds value.

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 no parameters, strong annotation coverage, and an output schema existing, the description covers the tool's purpose and scope adequately. It could elaborate on the format of the returned string, but that is likely in the output schema.

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 tool has 0 parameters, and schema coverage is 100%. Per guidelines, baseline score is 4 for no parameters, and the description does not need to add parameter details.

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 'Get information about defined memory regions and their permissions' using a specific verb and resource. It distinguishes from siblings by clarifying it shows regions defined with edb_set_memory_permissions, unlike generic memory map tools.

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 provides context by equating to EDB's DialogMemoryRegions view, implying it is for viewing permissions of regions set via edb_set_memory_permissions. However, it lacks explicit when-to-use or when-not-to-use compared to other memory tools.

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