edb_compare_sections

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is clear. The description adds specific behavioral context: it detects modifications (self-modifying code, patches) and returns a string. No contradiction with annotations, and the disclosure is useful beyond what annotations provide.

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 three concise sentences: purpose, detection capability, and equivalence. It is front-loaded with the primary action and contains no fluff. Every sentence serves a purpose.

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 tool with no parameters and an output schema present, the description adequately covers the core functionality. It specifies the return type but could be more explicit about the scope (e.g., 'all loaded sections'). Overall, it provides sufficient context for selection.

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 has 0 parameters with 100% coverage, so the description does not need to explain parameters. It implicitly indicates that the tool uses the current process state without requiring additional input.

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 clearly states the tool compares loaded memory sections with the original binary on disk to detect modifications. The verb 'compare' and specific resource ('loaded memory sections with the original binary') are explicit. It distinguishes from siblings like edb_binary_diff (binary vs binary) and edb_compare_memory (memory regions) by specifying the comparison target.

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 usage for detecting self-modifying code and patches, but it does not provide explicit guidance on when to use this tool versus alternatives like edb_binary_diff or edb_compare_memory. No when-not-to-use or exclusion criteria are mentioned.

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