agency-hosting_getWordPressSettingsV1

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

No annotations exist, so the description carries the transparency burden. It clearly signals a read-only operation with 'Returns' and discloses exactly what data fields are included, which goes beyond a bare 'gets settings' claim. It doesn't describe response formatting or error behavior, but the read-only nature and return content are clear.

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, tightly worded sentence with no filler. It front-loads the action and resource, then uses a concise list to convey the returned status categories without 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 simple read-only tool with one documented parameter and no output schema, the description adequately enumerates the returned information. It lacks response structure details and usage alternatives, but the tool's low complexity means this is largely sufficient.

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 only parameter, website_uid, is already well documented in the schema as 'Agency Plan website UID.' The description adds no new parameter-level detail beyond reinforcing the Agency Plan context, so the schema-heavy baseline of 3 is appropriate.

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 a specific verb ('Returns') and clearly identifies the resource: 'current WordPress settings for an Agency Plan website.' It also lists the exact fields returned, which distinguishes it from sibling tools like hosting_showMaintenanceStatusV1 or hosting_showLiteSpeedCacheStatusV1 that cover only individual statuses.

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 explicit when-to-use or alternative guidance is provided. The description implies the tool is for retrieving all four statuses at once, but it doesn't explicitly tell the agent when to choose this tool over the more granular sibling status endpoints.

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