ios_binary_strings

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only describes the extraction and filtering function without mentioning potential side effects, resource requirements, or performance characteristics. The tool is likely read-only, but this is not stated.

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 a single, dense sentence that front-loads the core action and immediately specifies the security relevance. No unnecessary words; every part 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 simple tool with 3 well-documented parameters and clear output expectations (list of filtered strings), the description is largely sufficient. It covers the input, the operation, and the filtering criteria. Lacking an output schema, a brief mention of the return format would improve completeness, but it is still adequate.

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 baseline is 3. The description adds value by listing specific pattern categories (e.g., 'AWS/Firebase/Google credentials') that elaborate on the filter enum's options, helping the agent understand what each filter value targets beyond the schema's brief descriptions.

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 states a specific verb ('extracts') and resource ('printable strings from an iOS app binary'), and explicitly mentions security-relevant patterns it filters for, such as URLs, API keys, and credentials. This clearly distinguishes it from sibling tools like ios_secrets_scanner, which may have a different focus.

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 does not provide any guidance on when to use this tool versus alternatives like ios_secrets_scanner or ios_frameworks_detector. It lacks explicit context for optimal usage, exclusions, or prerequisites, leaving the agent to infer when it should be invoked.

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