Discover Services

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

The annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only that access is over SSH, without explaining credential expectations, discovery scope, or what happens with the seemingly unrelated patterns and log_paths parameters.

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 only two short sentences with no filler, and the tool identity is front-loaded. The second sentence is vague but still brief and relevant.

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?

Although an output schema exists, this is a remote, credential-bearing tool with six parameters and ambiguous fields such as patterns and log_paths. The description does not provide enough context about authentication, scope, or how those parameters relate to service discovery.

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 100%, so the six parameters are documented in the schema and the baseline is 3. However, the description adds no meaning beyond the schema, and the schema itself includes confusing hints like "Search patterns (analyze_logs)" that the description does not clarify.

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 largely restates the name and title ("Discover services"), adding only a generic qualifier, "Remote system intelligence via SSH." It does not define what kinds of services are discovered or distinguish the tool from close siblings such as tm_system_get_info or tm_system_network_topology.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention prerequisites, credential requirements, or any conditions under which another sibling tool would be more appropriate.

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