ios_binary_strings

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

No annotations are provided, so the description carries the full behavioral burden. It discloses what classes of strings are returned but says nothing about whether the binary/IPA is modified (presumably read-only), how large binaries are handled, whether scanning is expensive, or what the response structure looks like — significant gaps for a binary-analysis tool with zero annotation coverage.

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 front-loaded sentence that names the action, the target artifact, and the filtering behavior with no filler. Every clause earns its place.

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?

With only three fully documented parameters and no output schema, the tool is simple enough that the description is close to sufficient. Still, it never characterizes the return value (a flat list of matching strings? grouped by category?) nor notes that the operation is read-only and non-destructive, which an agent must otherwise infer.

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?

Schema description coverage is 100%, so the schema already documents ipa_path, filter enum values, and min_length bounds. The description's pattern list loosely maps to the filter enum but adds no syntax, format, or interaction details beyond what the schema states, making the baseline of 3 appropriate.

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?

States a specific verb and resource ('Extracts printable strings from an iOS app binary') and enumerates the pattern classes it surfaces, so the tool's function is unambiguous. It never names or contrasts itself with the very similar ios_secrets_scanner / android_secrets_scanner siblings, so sibling differentiation is left to the agent.

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 security-analysis context is implied by the enumerated pattern types, giving an agent a reasonable sense of when to reach for it. However, there is no explicit when-to-use guidance and no statement of how it differs from ios_secrets_scanner, which appears to cover overlapping credential/secret detection.

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