answer_education_questionSearch BrightKey's cited answers to common international-education questions (curriculum, schools, universities, visas, process). Returns the best-match sourced answer.
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | Response language; defaults to en. | |
| query | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description aligns with annotations (readOnlyHint, openWorldHint). Adds context that it searches 'BrightKey's cited answers' and returns best-match, but does not disclose behavioral traits beyond what annotations already provide. No contradiction.
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, no wasted words. Purpose and result are front-loaded. Efficient and clear.
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 simple tool with one required param and no output schema, description covers purpose and result well. However, lacks details on answer format or citation style, which could be useful. Annotations and schema are present, so overall adequate.
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 50% (lang param described, query not). Description does not add meaning for parameters; does not clarify query format or lang options. Fails to compensate for the undocumented query parameter.
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?
Clearly states the verb 'Search' and the resource 'BrightKey's cited answers', with specific domain (international-education questions). Distinguishes from sibling tools like generic 'search' or 'fetch' by specifying it returns sourced answers.
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?
No explicit guidance on when to use this tool versus alternatives. Only implies use for international-education questions. Does not mention when not to use or compare with siblings like 'fetch' or 'search'.
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 clear, distinct purpose: answering questions, comparing universities, calculating ROI, fetching details, getting profiles, listing universities, matching schools, and searching. No overlap in functionality.
All tool names use snake_case and follow a verb_noun or noun_noun pattern, making them predictable. The only minor deviation is 'fetch', which is a single verb, but it's still clear and common for such operations.
8 tools is ideal for an education data server, covering core operations (search, list, profile, compare, ROI, etc.) without being overwhelming or insufficient.
The tool set covers main user needs: answering questions, searching and listing universities/schools, getting profiles and comparisons, and ROI calculations. Missing features like school comparison or data updates, but overall solid for a read-only knowledge base.