List EMQX Authenticators

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds semantic context by explaining the meaning of an empty authenticator chain, which helps the agent interpret results. It does not disclose any other behaviors (e.g., pagination, default limits), but for a simple no-parameter read-only tool, the added context is sufficient.

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 extremely concise: two short sentences (the first a noun phrase) plus a clear troubleshooting note. Every word earns its place, and the most actionable guidance ('Check this first...') is immediately visible. No fluff or redundancy.

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?

For a tool with no input parameters and an output schema (indicated by context), the description covers the key aspects: what the output represents, when to use it, and how to interpret the result. It is complete for its complexity and integrates well with sibling tools by providing a unique diagnostic role.

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 tool has zero parameters, so schema description coverage is 100% vacuously. The baseline for 0-parameter tools is 4, as there is no parameter information to provide. The description adds no parameter semantics because none are needed.

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 title clearly says 'List EMQX Authenticators', and the description specifies the resource and output: 'The authenticator chain and each authenticator's status.' However, the description itself lacks an explicit verb, relying on the tool name/title to convey the action. It does distinguish from siblings by focusing on authentication (authn) rather than authorization (authz) or other resources.

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?

Provides explicit when-to-use guidance: 'Check this first when devices cannot connect: an empty chain means EMQX has no user table, so every credential is rejected.' This gives clear diagnostic context and implies a troubleshooting workflow. It differentiates from other list tools by positioning itself as the first check for connection failures.

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