wordpress_get_comments

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

No annotations are provided, so the description must disclose behavioral traits fully. While 'Get' implies a read operation, the mention of filtering by 'post and status' is misleading because the input schema only allows a single 'perPage' parameter with additionalProperties false. The description does not clarify pagination behavior, return format, or that only perPage is accepted.

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, efficient sentence that front-loads the core action and resource. It is not verbose or repetitive, but it slightly sacrifices clarity by omitting parameter details. Still, its brevity is appropriate for a simple getter.

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 is a straightforward getter, but the description is incomplete given the lack of annotations and output schema. The single required parameter 'perPage' is unexplained, and the claimed filters are not reflected in the input schema. This leaves the agent without enough information to use the tool correctly.

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 schema coverage is 0% and the description provides no explanation for the 'perPage' parameter. The referenced filters 'post and status' are not present in the schema, so the description actively misleads about how to invoke the tool. The agent cannot determine the meaning or usage of the only available parameter.

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 action ('Get') and resource ('comments'), and adds the specific filtering context ('by post and status'). This distinguishes it from sibling comment tools like create/update/delete and from other getters for posts/pages/media.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, when not to use it, or why to choose it over other getters. The description only states what it does, not the context or exclusions.

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