wordpress_audit_hook_status

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

Discloses that secret is only partially returned (last 4 characters) and requires manage_options. No annotations, so description carries burden; it adds relevant behavioral context but does not cover side effects or rate limits.

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?

Description is efficient, listing returned fields and key details in one paragraph. The '[UNIFIED]' prefix adds minor clutter but is acceptable.

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?

Comprehensive for a read operation: lists returned fields, version requirement, and permission. Lacks return format details but given no output schema, it adequately informs the agent.

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?

Schema has one parameter 'site' with no description (0% coverage). The description does not explain the parameter meaning, format, or usage, providing no additional value beyond 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 clearly states it reads the audit-hook configuration, specifying the resource and verb. It lists the returned fields (endpoint_url, secret indicator, etc.) and distinguishes itself from sibling tools like wordpress_audit_hook_configure.

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?

Implies use for inspecting current settings, with mention of required permission (manage_options). No explicit when-to-use versus siblings or when-not-to-use.

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