edb_get_function_info

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, indicating safe read-only behavior. The description adds value by specifying the return content (address, prototype, source location) without contradicting 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 concise with two sentences plus structured arg/return details. It avoids verbosity but could be more standard (e.g., using proper JSON schema formatting). It earns its place without excess.

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 simplicity, the presence of an output schema, and the annotations, the description adequately covers the core functionality. It does not explain the return format in depth, but that is less critical due to 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 input schema includes a description for the 'name' property, and the description repeats an example. Although schema description coverage is reported as 0%, the schema itself provides meaning. The description does not add significant new semantic information beyond the schema.

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?

Description clearly states 'Get detailed info about a function' and specifies what information is included: address, prototype, source location. The verb 'Get' and resource 'function info' are specific, and the tool is clearly distinguishable from siblings like edb_get_function_bounds or edb_get_function_xrefs.

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 the tool is used to get function info, but provides no explicit guidance on when to use it versus alternative tools (e.g., edb_get_function_bounds) or when not to use it. No exclusions or context are given.

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