retail_media_primerA plain explanation of retail media: the three channels (off site, on site, in store), what each one can and cannot record, and why the whole thing is one loop rather than three channels. Useful even if you have no interest in Gus.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden of disclosing behavior. It states it's a 'plain explanation,' which implies a read-only, informational response. It doesn't explicitly mention lack of side effects, but for an educational primer the behavior is clearly non-mutating and self-contained.
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 two sentences that front-load the core purpose and list specific content points. Every word earns its place, with no filler or repetition.
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 simple informational tool with no parameters, no output schema, and no annotations, the description fully covers what the tool is, what topics it addresses, and even provides a usage note. No critical information is missing.
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, so the description has no obligation to explain parameter meanings. The baseline of 4 applies here since schema coverage is trivially complete and there are no parameters to clarify.
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 identifies the tool as providing a plain explanation of retail media, enumerating specific topics (three channels, recording capabilities, loop concept). It is distinct from sibling tools like ask_gus or gus_profile, which likely focus on Gus, by explicitly framing this as a conceptual primer.
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 phrase 'Useful even if you have no interest in Gus' implies the tool is for learning retail media fundamentals independently of the Gus context. While it doesn't explicitly state when to use this over siblings, the description gives a clear contextual trigger (wanting an explanation of retail media) and subtly contrasts with Gus-focused tools.
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.
Each tool has a clearly separate role: asking questions about Gus, viewing his professional profile, sending him a message, and learning about retail media. No two tools overlap in function, and the descriptions reinforce their distinct purposes.
All names are lowercase snake_case and readable, but they mix verb phrases (ask_gus, leave_a_note) with noun phrases (gus_profile, retail_media_primer). There is no consistent verb_noun pattern, so an agent cannot reliably predict tool names.
With only 4 tools, the server is well-scoped for its purpose. Each tool earns its place, covering Q&A, profile, contact, and educational content without unnecessary bloat.
The tool surface covers the core needs of the server: learning about Gus, reading his profile, asking questions, and leaving a message. The retail media primer adds educational value, and there are no obvious dead ends or missing essential operations.