wordpress_get_pages

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

The description implies a read-only operation ('abrufen'), but no explicit behavioral traits are disclosed beyond that. The limit parameter's default and maximum are stated, which adds some transparency. However, with no annotations, the description does not cover error behavior, authentication needs, or whether results are paginated. Overall, adequate but not thorough.

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 extremely concise, consisting of a single-sentence purpose and a list of two parameters. No unnecessary words. It is front-loaded with the main action.

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 the tool's simplicity (2 parameters, no output schema), the description covers the essentials. However, it lacks details on expected output format, potential errors, or any filtering options beyond limit. It is minimally complete but could be more informative.

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%, so the description must add meaning. It provides a brief explanation for connector_name and adds default and max value for limit. However, the description for connector_name ('Name des WordPress-Connectors') adds little beyond the schema title. The limit details are helpful but not extensive.

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 it retrieves pages from a WordPress site. The tool name 'get_pages' and the first sentence 'Seiten von einer WordPress-Site abrufen' directly indicate the resource (pages) and action (retrieve). This distinguishes it from siblings like wordpress_get_posts and wordpress_get_comments.

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 like wordpress_get_posts. There is no mention of prerequisites, context, or scenarios where get_pages is appropriate.

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