[CREATE] Get the current design brief, the active creative challenge. Call this or list_briefs FIRST if you want to submit a design. Returns brief ID needed for submit_design. Optionally filter by brand_slug.
| Name | Required | Description | Default |
|---|---|---|---|
| brand_slug | No | Optional brand slug to get that brand's current brief instead of the default RRG brief |
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 the return value (brief ID) but does not explicitly state that the tool is read-only, has no side effects, or require any permissions. For a getter, this absence of safety context is a notable gap.
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, front-loaded sentence that efficiently communicates purpose, usage timing, return value, and optional filtering. No unnecessary words or redundancy.
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 getter with one optional parameter and no output schema, the description provides the essential context: when to call it, what it returns, and how to filter. It does not cover behavioral details, but those are largely addressed by the tool's simplicity and schema, keeping this dimension strong.
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 schema already describes brand_slug with 100% coverage, explaining it filters to a specific brand's current brief. The description adds only 'Optionally filter by brand_slug,' which does not introduce new semantic meaning beyond the schema, so the baseline of 3 is appropriate.
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 function with a specific verb ('Get') and resource ('the current design brief'), and differentiates it from the sibling tool list_briefs by noting it returns the brief ID needed for submit_design. This makes the tool's purpose immediately obvious.
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 explicit usage context: 'Call this or list_briefs FIRST if you want to submit a design,' and notes the optional brand_slug filter. However, it does not specify conditions for choosing this tool over list_briefs beyond the 'current' versus listing all briefs, so it lacks full exclusion guidance.
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 with clear category tags. Minor potential confusion between get_current_brief vs list_briefs and get_brand vs get_brand_mcp_endpoint, but descriptions clarify intent.
All tools follow a consistent verb_noun pattern using lowercase with underscores, e.g., check_agent_standing, list_drops, submit_design. No mixing of conventions.
32 tools is on the high side, but the server covers a wide domain including browsing, purchasing, design submission, concierge, and marketing. Each tool serves a specific function, though some consolidation could be possible.
The tool surface covers the full lifecycle of browsing, purchasing, design creation, commissions, and concierge services. Minor gaps like refund handling are absent, but the core workflows are well-supported.