Get WordPress Site Info

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the tool's read-only nature is clear. The description adds transparency by specifying exactly which site details are returned, giving the agent expectation of output.

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 one well-crafted sentence that frontloads the action and resource, then lists concrete examples of returned data. No filler 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 read-only info tool with one optional parameter and annotations covering safety, this description is complete. It clearly states the tool's purpose, what it retrieves, and the source (Local by Flywheel WordPress site), which is sufficient for an agent to select and invoke it.

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 single parameter 'site' is fully described in the schema ('Site name, ID, or domain. Uses env var if not specified.'). The description does not add information about parameter formatting or defaults beyond what the schema provides, so it relies on the schema.

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 uses the specific verb 'Get' and names the resource as 'detailed information about the current Local by Flywheel WordPress site', enumerating key fields (URL, version, theme, PHP). This clearly distinguishes it from sibling tools like wp_list_sites (which lists sites) and mysql_query (which queries database).

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 site details but does not explicitly state when to choose it over alternatives such as wp_cli_run or mysql_query. There is no mention of exclusions or alternative contexts, leaving room for interpretation.

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