detect-existing-service

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

With no annotations, the description must disclose behaviors but is limited to 'Detect if a service is already installed'. It does not state whether the tool is read-only, requires permissions, or how it behaves when the service is not found. The lack of output schema further obscures the return value.

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 a single, concise sentence. It is well-front-loaded and avoids unnecessary words. However, the extreme brevity may sacrifice completeness, but given the tool's simplicity, it is appropriately sized.

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?

The description fails to specify what the tool returns (e.g., boolean, list of matches). Given no output schema, this gap is critical. Additionally, it does not address edge cases like multiple matches or when the service is not found. The tool's simplicity does not fully excuse the lack of return information.

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 coverage is 67%, and the description adds no parameter-level details beyond the schema. While the schema adequately defines three parameters, the tool description does not elaborate on their use or interaction, offering no additional value beyond the structured data.

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 function: detecting if a service is installed. The verb 'detect' and resource 'service' are specific. However, it does not differentiate from sibling tools like 'browse-services' or 'service-details', leaving ambiguity about the exact output (e.g., boolean vs. details).

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 no guidance on when to use this tool versus alternatives. For example, it does not suggest checking existence before deployment or distinguish from 'browse-services' which might list all services. The agent receives no contextual clues for optimal use.

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