edb_get_variable

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

Annotations already mark it as readOnly and idempotent. The description adds the 'current scope' context but does not disclose behavior for missing variables or other edge cases. No contradiction with 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?

The description is extremely concise, with two sentences for purpose and well-organized Args/Returns sections. Every word adds value, no fluff.

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 read-only variable tool, the description covers purpose, parameter, and return. It does not mention error handling or variable existence, but given the tool's simplicity and the presence of annotations and output schema, it is reasonably complete.

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 schema description coverage is reported as 0%, so the description must compensate. It provides a clear Args block with parameter name, type, and examples (e.g., 'i', 'argc', 'buffer'), adding value beyond the schema. It also documents the return type.

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 the specific verb 'Read' and identifies the resource as 'local or global variable in the current scope'. It clearly distinguishes from sibling tool 'edb_set_variable' (which writes), and from other read tools like 'get_register'.

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 states what it does (read a variable) but does not explicitly mention when to use it vs. alternatives like 'edb_set_variable' for writing, or 'edb_get_locals' for all locals. No exclusions or context hints are provided.

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