agency-hosting_getAgencyPlanWebsiteWordPressSettingsV1

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

With no annotations provided, the description must fully disclose behavior. It states the tool returns settings (a read operation), but does not mention side effects, authentication requirements, rate limits, or whether the data is live or cached. The description is adequate but lacks detailed behavioral context beyond the listed items.

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 sentence that efficiently lists the returned settings, with no wasted words. It is front-loaded and direct. However, it could be more structured (e.g., using a bulleted list) to improve readability, but it is not verbose.

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 low complexity (one parameter, no output schema). The description covers the tool's purpose and the items returned. However, it lacks details on the return format (e.g., data types) and does not clarify that this is specific to Agency Plan websites (though implied by the name). Siblings that return individual settings also hint at alternative granularity. Overall, mostly complete but with minor gaps.

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 one parameter 'website_uid' with a clear description. The tool description adds no additional meaning beyond the schema, and since schema coverage is 100%, the description adds no value for parameter semantics. Baseline 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 clearly states the tool returns current WordPress settings and lists four specific items (core version, LiteSpeed Cache plugin status, object cache status, maintenance mode status). It distinguishes from siblings that return individual settings (e.g., hosting_showWordPressCoreVersion) by being a consolidated 'get all' tool.

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 getting a summary of key WordPress settings, but provides no explicit guidance on when to use this versus calling individual getter tools. There is no mention of alternatives or when not to use it, leaving the agent to infer usage context.

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