Metro Logs MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the IDB installation requirement, which is useful context about dependencies. However, it fails to describe critical behavioral aspects such as whether this operation is safe/read-only or destructive, what happens if the simulator isn't running, error conditions, or the expected response format. For a tool that interacts with simulators, this leaves significant gaps.

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 concise with just two sentences that each serve a distinct purpose: the first states the core functionality, and the second provides a critical prerequisite. There's no wasted language, and the information is front-loaded with the primary action. This is an excellent example of efficient communication.

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 complexity of interacting with iOS simulators and the absence of both annotations and an output schema, the description is insufficiently complete. It mentions the IDB requirement but omits other critical context such as error handling, what constitutes valid keycodes, whether the tool waits for completion, or what the return value looks like. For a tool with no structured safety or output information, the description should provide more operational guidance.

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?

The input schema has 100% description coverage, with both parameters ('keycodes' and 'udid') clearly documented in the schema itself. The description adds no additional parameter information beyond what's already in the schema descriptions. According to the scoring rules, when schema coverage is high (>80%), the baseline score is 3 even without parameter details in the description.

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 action ('Send a sequence of key events') and target resource ('to an iOS simulator'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'ios_key_event' (which likely sends single key events rather than sequences), leaving some ambiguity about when to choose this specific tool.

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 some usage context by mentioning the prerequisite ('Requires IDB to be installed'), which is helpful for setup. However, it offers no guidance on when to use this tool versus alternatives like 'ios_key_event' or 'ios_input_text', nor does it specify scenarios where key sequences are preferred over other input methods.

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