annotation.define_data_var

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

No annotations are provided, so the description carries full burden. It fails to disclose any behavioral traits: does it create a new variable, overwrite existing, require specific permissions, or have side effects? The description is completely silent on behavior.

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 only one sentence, which is under-specified for a tool with five parameters and no supporting schema descriptions. It lacks necessary detail, not truly concise.

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?

Given the tool's complexity (5 params, 2 required, no output schema, many sibling tools), the description is wholly inadequate. It does not explain what the tool does in the context of binary analysis, what the parameters represent, or the expected outcome.

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%. The description adds no meaning to the five parameters (name, width, address, type_name, session_id). An agent has no idea what these parameters mean or how they affect the operation.

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 'Define data variable,' which roughly restates the tool name. It identifies the verb and resource but does not distinguish from sibling tools like 'annotation.define_symbol' or 'annotation.rename_data_var.' No context about what a data variable is or how it differs from other symbols.

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 versus alternatives such as 'define_symbol' or 'rename_data_var.' No prerequisites (e.g., session must be open, address must be valid) or when-not-to-use scenarios are provided.

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