wordpress_get_page

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

With no annotations, the description must disclose all behavioral traits. It only states the function ('Get') but omits details such as authentication requirements, error handling (e.g., page not found), rate limits, or any side effects. The description is insufficient for an agent to understand the tool's behavior beyond a simple read.

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, front-loaded sentence that efficiently communicates the core purpose. It earns its place without verbosity, but could include slightly more detail without sacrificing conciseness.

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?

For a tool with no output schema, no annotations, and two parameters (one undocumented enum), the description is too sparse. It does not explain what the response contains, the meaning of the context parameter, or any usage considerations. The description is incomplete for an agent to understand the full context of the call.

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 0% description coverage, so the description needs to add meaning. It mentions 'by ID' for the id parameter but does not explain the 'context' parameter (enum: view/edit), its purpose, or how the response differs based on it. The description adds minimal 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 the verb 'Get', the resource 'WordPress page', and the method 'by ID from the configured site'. It distinguishes this tool from siblings like wordpress_get_post (for posts) and wordpress_list_pages (for listing), making its purpose specific and unambiguous.

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 are sibling tools like wordpress_get_post for posts and wordpress_list_pages for listing, but the description does not mention these or any criteria for choosing this tool.

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