fetch_wordpress_info

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states it 'fetches' and returns a dict, without mentioning any behavioral traits such as required authentication, rate limits, side effects, or the structure of the response. This is a significant gap for a tool that likely requires interaction with an external API.

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 very concise—two sentences and 28 words. It front-loads the core purpose. However, it could be slightly longer to include behavioral or return details without becoming verbose. It earns its place but is not maximally informative.

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 absence of an output schema and annotations, the description should provide more details about what 'site information' includes. It only says 'dict[str, Any]' without specifying the actual keys or structure. This is insufficient for an agent to understand what it will receive.

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 tool has zero parameters, and schema description coverage is 100% (trivially). The description adds no parameter info, but the baseline for 0 parameters is 4, and it does not fall short of that.

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 states 'Fetch WordPress site information', which clearly identifies the action and resource. However, it does not differentiate from sibling tools like fetch_categories or fetch_pages, which also fetch specific types of information. The verb 'fetch' and resource 'site information' are clear but generic.

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?

The description provides no guidance on when to use this tool versus its siblings. It lacks explicit context about use cases, prerequisites, or alternatives. For example, it does not mention that fetch_page_by_id should be used for individual pages or that fetch_posts_by_category is for category-filtered posts.

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