get_seo_data

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions what data is retrieved but does not describe behavioral traits such as read-only nature (implied by 'Get'), error handling, permissions required, rate limits, or response format. This is a significant gap for a tool with no annotation coverage.

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 lists key data fields, making it front-loaded and easy to scan. However, it could be slightly more structured by separating the purpose from the data list for better clarity, but it avoids unnecessary verbosity.

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 annotations and no output schema, the description is incomplete. It specifies what data is retrieved but lacks details on return format, error cases, or behavioral context. For a tool with 1 parameter and no structured output information, more guidance is needed to ensure proper agent usage.

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 100% description coverage, with 'post_id' clearly documented. The description adds minimal value beyond the schema by implying the parameter is used to fetch SEO data for a specific post/page, but does not provide additional context like format examples or constraints. Baseline 3 is appropriate as the schema handles most of the parameter 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 the tool's purpose: 'Get Rank Math SEO data for a post/page' with specific data fields listed (SEO title, meta description, etc.). It uses a specific verb ('Get') and resource ('Rank Math SEO data'), but does not explicitly distinguish it from sibling tools like 'get_seo_status', which might be related but not clearly differentiated.

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 alternatives. It does not mention sibling tools like 'get_seo_status' or 'update_seo_data', nor does it specify prerequisites, contexts, or exclusions for usage, leaving the agent to infer based on the name alone.

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