authenticate-wp

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

With no annotations, the description must convey behavioral traits. It only says 'connect with credentials' and does not disclose whether credentials are stored, how long the session lasts, or whether any state changes occur on the site. This lack of transparency is a significant gap for an authentication tool.

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 with no unnecessary words. It is well-structured and front-loaded with the key action and resource. While it is minimal, it is not verbose or redundant, earning a high score for conciseness.

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 tool has no output schema and no annotations, so the description is the only source of contextual information. It fails to explain what the tool returns (e.g., token, success status) or how it behaves (e.g., session persistence). The existence of 'test-wp-connection' as a sibling makes contextual guidance important, but none is given.

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 input schema has 100% parameter description coverage, including the preference for app passwords. The description itself adds no additional parameter meaning, so the baseline score of 3 is appropriate since the schema carries the semantic load.

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 purpose: 'Connect to a WordPress site with credentials.' It identifies the resource (WordPress site) and the action (connect), making it distinct from generic operations. However, it does not explicitly differentiate from the sibling 'test-wp-connection' tool, which could be seen as similar.

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?

No usage guidance is provided. The description does not mention when to use this tool instead of 'test-wp-connection', whether it must be called before other WordPress operations, or any prerequisites or alternatives.

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