Platform & plugins

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

No annotations are provided, so the description must disclose behavioral traits. It lists what is returned but does not mention side effects, authorization needs, or whether the operation is read-only. The description provides some transparency but 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 a single sentence that efficiently lists the output components. It is concise but could be more structured or broken into a bullet list for clarity. No unnecessary 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?

With no output schema, the description adequately explains the return values. It covers the main categories of returned data. However, it lacks details on whether performance impact exists or if the data is real-time vs cached, but given the tool's simplicity (one parameter), it is largely complete.

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% for the single parameter (profileId), so baseline is 3. The description does not add any additional meaning beyond what the schema already provides; it only describes the output.

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 specifies what the tool returns: server brand/version, Minecraft version, plugin/mod list, config file names, and key config highlights. This is a specific verb+resource that distinguishes it from sibling tools like diagnose or get_health.

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 implies the tool is for retrieving platform information but does not explicitly state when to use it vs. alternatives, nor does it provide when-not-to-use guidance or mention sibling tools. Usage context is implied but not clarified.

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