address_name

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

Annotations carry the safety profile (idempotent, non-destructive, closed-world), so the description could add value with real behavior—what happens when no symbol exists at the address, whether it falls back to a synthesized label, whether debug info or dynamic symbols are consulted—but it says nothing. Note the tension between the verb "Read" and readOnlyHint=false; the analysis_project_id parameter plausibly explains the side effect (result retention), but the description never reconciles it.

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?

A single front-loaded sentence with zero filler. Brevity is achieved, though partly by omitting needed content rather than by discipline.

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?

There is no output schema, so the description must convey what an agent gets back—a symbol string, a null, a fallback—and it does not. Combined with the undocumented document parameter and the unstated open-binary prerequisite, an agent can only call this correctly by guessing.

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 only 33%, and the description compensates for none of it. The required address parameter has only a regex pattern and no explanation of accepted forms (module:offset vs raw hex), and the optional document parameter is entirely undocumented in both schema and description.

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?

"Read the symbol name at an address" states a specific verb and resource, and "in the active ELF analysis" scopes it to the open binary session. It does not differentiate from nearby siblings such as list_names, address_to_file_offset, or map_native_address, which an agent could plausibly confuse it with.

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?

There is no guidance on when to choose this over list_names (bulk listing) or map_native_address, and no stated prerequisite that a binary must first be opened via open_binary. The only hint of context is the phrase "active ELF analysis," which implies far more than it explains.

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