binary.strings

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only says 'list discovered strings with pagination', which is a read operation, but does not mention if it requires a session, whether it is idempotent, how strings are discovered (e.g., does it trigger analysis?), or any side effects. For a tool with no annotations, this is insufficient behavioral context.

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 extremely short (4 words) and front-loaded. However, it is under-specified for a tool with 3 parameters and no annotations. While no word is wasted, it fails to pay rent by not adding value beyond the tool name and parameter names. The conciseness lowers usability.

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 tool's moderate complexity (3 parameters, no output schema, no annotations, 0% schema coverage), the description is incomplete. It does not explain the output format, how strings are ordered, whether pagination is cursor- or offset-based, or the relationship between session and strings. The agent cannot reliably use this tool without external documentation.

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 0%, so the description must compensate. It mentions pagination (implying limit and offset) but does not name the parameters or explain what 'session_id' is used for (e.g., to select the session/binary). The description adds minimal meaning beyond the raw schema, leaving the agent to guess the role of 'session_id' and whether limit/offset are standard or have hidden constraints.

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 'List discovered strings with pagination' clearly states it lists strings, but does not specify which binary or context the strings belong to. It distinguishes from sibling tools like 'binary.summary' or 'binary.sections', but there is no mention of what entity the strings are discovered from (e.g., a loaded binary). The purpose is adequate but ambiguous about scope.

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?

No guidance on when to use this tool versus alternatives like 'search.data', 'search.next_text', or 'binary.search_text'. The description implies usage for paginating through discovered strings, but there is no mention of prerequisites (e.g., a session must be open, analysis must be complete) or when not to use it. The agent has no help selecting this over the many string-related siblings.

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