pwndbg_bins

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

No annotations provided, but description discloses basic behavior (prints bin contents, optional addresses). Lacks details on side effects or permissions, but it's a simple read command.

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?

Very concise: one-line summary, source info, explanation, then args list. No fluff, front-loaded.

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 output schema exists, description adequately explains tool purpose and optional params. Could mention contrast with sibling tools but not necessary.

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?

Description adds meaning by listing 'session_id: The UUID', 'addr: Optional arena address', 'tcache_addr: Optional tcache address', while schema only has type and title. Compensates for 0% schema coverage.

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?

Description clearly states 'Print all bin contents — fast, small, large, unsorted, and tcache' with verb+resource. It lists specific bin types and distinguishes from siblings by mentioning 'unified view' and 'all bin types'.

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?

Implies usage for comprehensive overview vs individual bin tools like pwndbg_fastbins, but lacks explicit when-not or alternative recommendations. Still clear enough for agent.

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