wp_get_activity_log

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

No annotations are provided, and the description does not disclose any behavioral traits. It does not state whether the tool is read-only, destructive, requires authentication, or what the response format is. The description adds no behavioral context beyond the basic action.

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, making it concise. However, it omits important details that should be present, such as parameter explanations or usage context. It is under-specified rather than efficiently structured.

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?

Given no output schema, no annotations, and four parameters with no descriptions, the description is severely incomplete. An agent cannot determine the return format, behavior, or proper parameter usage. The tool's complexity is low, but the description fails to provide essential context.

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 four parameters (page, per_page, action, object_type) with zero schema descriptions (0% coverage). The description only mentions 'optional filters' but does not explain what each filter does or its format. This minimal addition does not compensate for the lack of schema documentation.

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 what the tool does: 'Get MCP activity log with optional filters'. The verb 'Get' and resource 'MCP activity log' are specific. However, it does not differentiate from other get/list tools like wp_get_settings or wp_get_site_info, which are separate resources. Still, the purpose is clear.

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 guidance on when to use this tool versus alternatives. Among many sibling tools like wp_list_posts or wp_health_check, there is no mention of use cases or contexts where this log retrieval is appropriate. The description is purely functional.

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