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

The description adds significant behavioral context beyond the annotations. Specifically, it details the 1MB file cap implemented to prevent memory blowup and the resulting 'truncated=true' flag, which are vital for operational correctness.

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 highly dense but effective. It front-loads the core functionality and flows logically into operational constraints (file cap), prerequisites (manage_options), and failure conditions (disabled status). It efficiently uses space.

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 definition is extremely complete. It covers file source, default behavior, maximum limits, resource management (1MB cap), input filtering, and expected failure states, providing everything an agent needs.

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?

While schema coverage is 100%, the description clarifies the specific semantics of the filter, stating it is 'optionally filtered by a case-insensitive substring' applied 'before the last-N slice,' adding meaningful operational context to the parameters.

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's function: 'Read the tail of wp-content/debug.log.' It provides a specific file path and operation, making its purpose unmistakable.

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?

It provides critical operational guidance by explaining how the agent can determine the tool's usability: 'Returns status="disabled" with instructions when WP_DEBUG_LOG is not enabled in wp-config.php.' This is crucial for correct usage.

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