flash_info

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

No annotations are provided, so the description bears full responsibility. The verb 'Display' implies a non-destructive read operation, but it does not explicitly state the absence of side effects or other behavioral traits (e.g., permission requirements).

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 sentence concisely conveys the tool's purpose and output details without extraneous information. It is front-loaded and efficient.

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 simple informational tool with one parameter and an output schema, the description covers the basic output fields but omits parameter guidance and usage context. While not severely incomplete, it lacks sufficient detail for optimal agent decision-making.

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 schema has one parameter 'bank', but the description provides no information about its meaning, valid values, or role. With 0% schema description coverage, the description fails to compensate, leaving the parameter ambiguous.

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 'Display information about the flash bank (size, sectors, erase state)', using a specific verb and resource. It distinguishes itself from sibling tools like flash_erase_sector or flash_write by indicating a read-only, informational purpose.

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 to view flash bank details but lacks explicit guidance on when to use this tool versus alternatives. No exclusions or alternative recommendations are provided, relying on the agent to infer context.

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