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

The description goes well beyond the annotations: it explains that each call resets the password, invalidates the previous one, signs out existing sessions, and that the value is shown once and not stored. This adds critical side-effect and secrecy context that destructiveHint alone cannot convey.

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?

Four tight sentences, front-loaded with the resource, then the routing rule, then the side effects, then the handling instruction. Nothing is redundant and each sentence adds actionable information.

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?

There is no output schema, and the description compensates by stating exactly what the caller receives (username and a newly generated password) and how to handle it. For a single-parameter mutation tool, nothing an agent needs to call it safely is missing.

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?

Only one parameter (projectId) exists, but schema description coverage is 0% and the description never explains what projectId refers to or how to obtain it. The description is otherwise rich, but parameter meaning is left entirely implicit, so it only meets the minimum viable bar.

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?

States a specific verb and resource: 'WordPress admin login details for a project's hosted site: the admin username and a NEW password'. It is immediately distinguishable from the sibling uichemy_open_site_admin, which is named directly.

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?

Explicitly defines the trigger ('only call it when the user asks for the username/password or login details') and names the alternative for the other case ('to just get into the admin now, use uichemy_open_site_admin'). Both when-to-use and when-not-to-use are covered.

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