MCPEmulate

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it explains the two modes with their effects (log and return default_return vs. log and stop emulation), mentions idempotency ('replaces existing hook'), and implies mutation (installing a hook). However, it doesn't cover permissions, rate limits, or error conditions.

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 efficiently structured with clear sections (overview, modes, idempotency note, args), uses bullet-like formatting without markdown, and every sentence adds value. It's appropriately sized for a tool with three parameters and no annotations.

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 (mutation with parameters), no annotations, and no output schema, the description is nearly complete. It covers purpose, behavior, and parameters well, but lacks details on return values, error handling, or integration with sibling tools like 'get_syscall_log'. Still, it provides sufficient context for basic use.

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 fully. It successfully adds meaning beyond the bare schema by explaining all three parameters: 'session_id' (context), 'mode' (options and defaults with behavioral implications), and 'default_return' (purpose and default). This provides complete semantic understanding despite the schema's lack of 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 clearly states the specific action ('Install a syscall hook to intercept system calls') and distinguishes it from sibling tools like 'unhook_syscall' and 'get_syscall_log'. It uses precise technical terminology that identifies both the verb (install/intercept) and resource (syscall hook).

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 implies usage through the explanation of modes ('skip' and 'stop'), suggesting when each might be appropriate, but doesn't explicitly state when to use this tool versus alternatives like 'unhook_syscall' or other debugging tools. No explicit exclusions or prerequisites are mentioned.

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