MCPEmulate

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

No annotations are provided, so the description carries full burden. It discloses that the tool creates a new session and restores state, implying mutation, but lacks details on permissions, side effects (e.g., overwriting existing sessions), error handling, or rate limits. The description adds basic behavioral context but is insufficient for a mutation tool with no 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?

The description is appropriately sized and front-loaded: the first sentence states the core purpose, followed by a brief elaboration and parameter details. Every sentence adds value without redundancy, and the structure is clear with a heading for args.

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 no annotations, no output schema, and 2 parameters with 0% schema coverage, the description is moderately complete. It covers the tool's purpose, usage context, and parameter semantics adequately, but lacks details on behavioral aspects like error conditions or return values, which are important for a mutation tool in a debugging/session management context.

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 adds meaningful semantics for both parameters: 'arch' is explained as 'Architecture name (must match the exported state's arch)' and 'state' as 'The state dict from export_session'. This clarifies purpose and constraints beyond the bare schema, though it could include examples or format details for the state dict.

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 tool's purpose with specific verbs ('import', 'creates', 'restores') and resources ('session state', 'new session', 'architecture'), and distinguishes it from sibling tools like 'export_session' by specifying it restores state from export. It explicitly mentions the relationship to 'export_session' for the state parameter.

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 provides clear context for when to use this tool: to create a new session and restore state from an export. It implies usage after 'export_session' by referencing 'state dict from export_session', but does not explicitly state when not to use it or name alternatives among siblings like 'create_emulator' or 'restore_context', which could be relevant for session management.

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