Register Product

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

Annotations are all false, so description carries the burden. It discloses that the tool creates a new listing, returns an owner_token to be saved, and optionally accepts MCP config for discoverability. No destructive side effects or contradictions with annotations.

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?

Two sentences with no wasted words. First sentence states the core action; second sentence adds critical guidance on token storage and optional config. Every sentence earns its place.

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 complexity (7 parameters including nested objects, no output schema), the description covers the essential return value (owner_token) and key usage. It could be slightly improved by explicitly noting that agent_services is optional, but the schema already handles that. Overall, it is sufficiently complete.

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 100% but description adds significant value: it highlights the required fields (name, description, url), explains the return of owner_token and its importance for updates, and provides concrete JSON examples for mcp_config config. This goes well beyond the schema's basic descriptions.

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 'Register a new product, service, or business in Sylex Search' with a specific verb and resource. It distinguishes from siblings like manage.update (update) and search.discover (search) by emphasizing creation and the unique owner_token return.

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 instructs to store the owner_token for later updates, implying this tool is for initial registration, not updates. It also mentions optional MCP config for future connectivity. However, it does not explicitly state when not to use it or name alternative tools for different actions.

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