check_security

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 lists the security features checked but does not disclose whether the tool modifies files or requires special permissions. It is implied to be read-only, but this is not stated explicitly.

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, listing features per format in bullet-point style. It contains no filler and front-loads the main purpose. Minor improvement could be more structured formatting, but it is 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?

Given the single parameter and existence of an output schema, the description adequately explains what the tool does and what it returns ('Security feature detection results'). It covers the essential information for a security checking tool.

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?

With 0% schema description coverage, the description adds meaning beyond the schema. The schema only provides 'File Path' as a title, while the description specifies 'Absolute path to the binary file', clarifying the expected input format and nature.

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 checks security features of a binary file, listing specific features for ELF, PE, and Mach-O formats. It uses a specific verb ('check') and resource ('binary file'), and distinguishes itself from sibling tools that focus on disassembly, ROP gadgets, or string extraction.

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 mentions it is 'similar to the checksec tool', providing context for users familiar with that tool. However, it does not explicitly state when to use this tool over alternatives (e.g., for quick security assessment versus detailed analysis), nor does it specify when not to use it.

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