Electron app info

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

Annotations declare readOnlyHint=true, and description adds detailed behavioral context: code-signature behavior (verified for packaged macOS, unknown for unpackaged/dev, unsupported off macOS), and error conditions with non-retryable nature. This surpasses what annotations provide, fully informing the agent of side effects and constraints.

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?

Description is well-structured: first sentence defines output, then parameter guidance, return shape, and errors. It is somewhat lengthy but every sentence adds value. Slight reduction possible, but front-loaded purpose and clear organization earn a 4.

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?

No output schema, but description fully outlines return fields (ok, session_id, transport, versions, app, signature, capabilities) and error conditions. For a simple info-reporting tool, this provides complete context. Sibling tools are all different operations, so no overlap confusion.

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 covers 100% of parameters with description for sessionId. Description goes further by explaining the parameter's role ('target a specific session when several are running') and when to omit ('Omit when a single session is running'), adding practical usage context beyond the schema.

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 begins with 'Report the running Electron app environment,' specifying the verb (report) and resource (Electron app environment). It lists exact data returned (runtime versions, app name/paths, etc.), clearly distinguishing it from sibling tools that focus on UI interaction or process control.

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?

States when to use: to get environment info. Provides explicit instruction for sessionId parameter (omit if single session, pass if multiple). Lists specific error types (NOT_RUNNING, BAD_ARGUMENT) with actionable advice (call electron_launch first, pass sessionId). No alternatives mentioned, but errors serve as when-not-to-use guidance.

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