search_siteSearch the canonical Afromorphism website. Results include attribution and canonical URLs.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | Yes | ||
| category | No | ||
| contentType | No | ||
| updatedFrom | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds that results include attribution and canonical URLs, which is useful output context. However, it does not disclose pagination behavior, result limits, or any other operational nuances, so value added is moderate.
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 two short sentences, front-loaded with the action ('Search') and resource. It is concise, contains no filler, and every word contributes to defining the tool's core function.
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?
With 5 parameters, no schema descriptions, and no output schema, the description is too minimal. It does not explain search semantics, filtering options, or result format beyond attribution and canonical URLs, leaving significant gaps in operational understanding.
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 0% and the description provides no information about parameters. It does not explain query, limit, category, contentType, or updatedFrom beyond the schema's type/constraints, leaving the agent without semantic guidance for parameter usage.
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 searches the canonical Afromorphism website, a specific verb and resource. It distinguishes itself from siblings like get_article and lookup_glossary by being the general site search, and mention of attribution and canonical URLs adds clarity.
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?
Usage is implied by the name and description—use this to search across the site—but there is no explicit guidance on when to choose it over alternatives like get_article or lookup_glossary. No exclusions or alternative tool names are provided.
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 targets a distinct action: retrieving a single article, listing recent articles, looking up glossary terms, searching the site, and getting site metadata. There is no overlap or ambiguity between them.
Four tools follow a clear verb_noun pattern (get_article, list_recent_articles, lookup_glossary, search_site), but 'site_information' deviates by using a noun phrase without a verb. Overall the pattern is mostly consistent and predictable.
Five tools is a well-scoped set for a content-focused site. Each tool provides a distinct capability without unnecessary overlap or bloat.
The set covers core content retrieval needs: single article, recent articles, glossary, and site-wide search. Minor gaps like a dedicated category/tag listing could exist, but the current surface handles typical browsing workflows well.