wordpress_wp_core_verify_checksums

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

No annotations provided, so description carries full burden. While 'verify' and 'detecting' imply read-only behavior, it fails to explicitly state whether this modifies files, what the output format is (list of files? boolean?), or whether it requires specific permissions.

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?

Two sentences that earn their place. The '[UNIFIED]' prefix appears to be metadata leakage but doesn't severely impact readability. Otherwise efficient structure.

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?

Simple single-parameter tool, but missing critical documentation for that parameter. Also lacks output description (what constitutes a failure? return format?) despite having no output schema. Needs param documentation to be complete.

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 coverage is 0% and description completely omits documentation for the single required 'site' parameter. No guidance on expected format (URL? domain? path?) or how to identify the target site.

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?

Clear specific verb (verify) and resource (WordPress core files) against specific reference (official checksums). Explicitly distinguishes from sibling 'wordpress_wp_plugin_verify_checksums' by specifying 'core files'.

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?

Provides context that this is a 'Critical security tool for detecting tampering', implying security audit usage. However, lacks explicit when-not guidance or alternatives (e.g., when to use repair vs verify).

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