goji_explain_termExplain a marketing, SEO, AEO, web or branding term the way GOJI defines it — in plain English, with why it matters, how it works and what to do about it. Covers every term in GOJI's plain-English glossary. Accepts an acronym or the full name ("AEO" or "answer engine optimisation").
| Name | Required | Description | Default |
|---|---|---|---|
| term | Yes | The term to explain |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It adds useful details about input handling (accepts acronym or full name) and the style of output (plain English with why/how/action), but it does not disclose the return format (e.g., plain text vs. structured) or behavior for unknown terms. This is a moderate disclosure, lacking some specifics.
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 concise: two sentences that front-load the core purpose ('Explain a marketing... term') and then add essential details about coverage and input flexibility. Every sentence 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 single-parameter tool with no output schema, the description covers the key aspects: what it explains, the scope (glossary), input variations, and the structure of the content (why/how/action). It indirectly implies the return content through 'explain... with why it matters, how it works and what to do'. It lacks an explicit statement of return format or error handling, but overall it is sufficiently complete for this simple tool.
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% (the parameter 'term' is described), so the baseline is 3. The description adds meaning by specifying the domain (marketing, SEO, AEO, web, branding) and mentioning that acronyms or full names are accepted, which goes beyond the schema's simple 'The term to explain'. This added semantic context justifies a 4.
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 explains marketing, SEO, AEO, web, or branding terms in plain English, with specific components (why it matters, how it works, what to do). This is a specific verb+resource combination that distinguishes it from siblings like goji_browse_glossary or goji_search, which focus on browsing or searching rather than explaining a single term.
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 clear context: it covers every term in GOJI's plain-English glossary and accepts acronyms or full names, telling users when this tool is appropriate. It does not explicitly mention when not to use it or name alternatives, but the purpose is well-scoped and distinct from siblings, so it meets the 'clear context, no exclusions' bar.
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.
Tools map to distinct content types (FAQ, glossary, guide, chapter, service), and descriptions give clear usage cues. goji_answer_faq and goji_search overlap in content coverage, but their intended use cases ('best for how much/how long' vs 'use first when you don't know the page') reduce ambiguity.
Eight tools use the goji_ prefix with a clear verb_noun structure (answer_faq, browse_glossary, explain_term, get_service, read_guide, read_guide_chapter, start_enquiry). goji_guide_contents is a noun phrase and goji_search is a bare verb, so the pattern is not perfectly uniform.
Nine tools is a reasonable, focused set for a content-retrieval and enquiry server. Each tool covers a distinct access pattern—search, list, read, explain, and contact—without bloat.
The surface covers FAQ lookup, glossary browsing, term explanation, service info, guide TOC and chapter reading, and enquiry submission. Agents can navigate from general search to specific pages and then take a contact action, leaving no dead ends.