compare_elf_to_flash

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

No annotations are provided, so the description carries the full burden. It discloses the read-only behavior by saying it 'reads' ELF sections and target memory, and explains the comparison algorithm. It doesn't detail side effects or exact reporting format, but given it is a read-only verification tool, this is adequate.

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 sentences, each earning its place: what it does, how it does it, and when/with what prerequisites to use it. No fluff, no repetition of schema or title.

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?

The description covers purpose, methodology, use case, and prerequisites. There is no output schema, but 'reports mismatching bytes' hints at the result. It could be more explicit about the return format or error behavior, but for a focused comparison tool this is sufficiently 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 tool has zero parameters, so there is nothing for the description to explain beyond what the empty schema already shows. Baseline for no-parameter tools is 4, and no additional semantics are needed.

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 a specific verb ('Compare') with a clear object ('all loadable ELF sections' vs 'actual target memory'), and further details the comparison by mentioning PROGBITS+ALLOC sections. This clearly distinguishes it from sibling tools like inspect_project_memory or write_project_memory.

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?

It explicitly states the intended use case ('verifying that flash programming completed correctly') and prerequisites ('Requires ELF loaded and probe connected'). It does not mention alternatives or when not to use it, but the context is clear enough.

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