Metro Logs MCP

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

No annotations are provided, so the description carries the full burden. It discloses that the tool toggles the inspector programmatically and mimics a manual action, which is helpful context. However, it lacks details on behavioral traits like side effects (e.g., whether it affects app state), permissions needed, or error conditions. The description does not contradict any annotations.

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 front-loaded with the core purpose in the first sentence, followed by a practical analogy and use case. Both sentences earn their place by clarifying functionality and utility, with zero wasted words.

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 low complexity (0 parameters, no output schema, no annotations), the description is complete enough for basic understanding. It explains what the tool does and why to use it. However, it could be more complete by addressing potential behavioral nuances like toggle state persistence or compatibility issues, which are relevant for a debugging tool.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, maintaining focus on the tool's purpose. Baseline is 4 for 0 parameters, as the description adds value without unnecessary details.

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 ('Toggle React Native's Element Inspector overlay programmatically') and the resource involved ('Element Inspector overlay'). It distinguishes from siblings by focusing on toggling the inspector rather than other debugging or interaction tools like 'get_inspector_selection' or 'inspect_component'.

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 usage ('Useful for enabling inspector features without user interaction') and references manual alternative ('same as manually doing: Dev Menu > Toggle Element Inspector'). However, it does not explicitly state when NOT to use this tool or name specific alternative tools from the sibling list.

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