Generate SEO metadata, heading structure, keyword clusters, FAQ ideas, and internal-link targets for a page.
| Name | Required | Description | Default |
|---|---|---|---|
| topic | Yes | Page or article topic. | |
| audience | No | Optional target audience. | |
| pageType | No | service, blog, resource, category, product, or landing. | |
| primaryKeyword | No | Primary SEO keyword. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds no behavioral traits beyond these, which is acceptable but does not enhance the agent's understanding of side effects or permissions.
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?
Single sentence, no filler. Every word adds value, and the description is front-loaded with the action and outputs.
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 read-only, idempotent tool with 4 well-documented parameters and no output schema, the description covers the main outputs. It could mention the return format (e.g., structured JSON), but overall it is sufficient.
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 description coverage is 100%, with all 4 parameters documented. The description does not add new meaning beyond the schema (e.g., it does not explain format or constraints). Baseline 3 is appropriate as schema handles the semantics.
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 generates SEO metadata, heading structure, keyword clusters, FAQ ideas, and internal-link targets for a page. It uses a specific verb and lists the outputs, but does not differentiate from sibling tools like blog_generator that may also produce SEO content.
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 on when to use this tool versus alternatives. It does not specify context, prerequisites, or when not to use it. Sibling tools like blog_generator or generate_service_recommendation could overlap, but no exclusions are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes (e.g., blog_generator vs. get_blog_post), but there is overlap among some content validation tools (csv_cleaner, duplicate_sku_finder, inventory_checker, product_catalog_validator) which could cause confusion. Also, compare_services and search_services serve similar functions.
Tool names mix styles: some use noun_verb (amazon_listing_manager), others verb_noun (compare_services), and there are multiple prefixes like get_, search_, list_. This inconsistency may hinder an agent's ability to predict tool names.
With 35 tools, the set is large and covers many subdomains. This could overwhelm an agent, making selection challenging. A more focused subset would improve coherence.
The tools cover a broad range of ecommerce operations: listing management for multiple platforms, content generation, data validation, research, and reporting. However, missing update/delete capabilities and some platform interactions limit full lifecycle coverage.
