BEREAN.AI

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 adequately reveals output length (250-400 words), style (pastoral, Reformed theology), and inclusion of Scripture references, setting expectations for the response. It does not cover potential limitations or edge cases, but for a question-answering tool this is sufficient.

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 sentences, front-loaded with the primary action and key attributes, followed by usage guidance. Every word earns its place—no redundant or irrelevant information.

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?

Despite having no output schema and no annotations, the description provides sufficient context for a simple tool: purpose, response format, style, and usage scenarios. It could be more explicit about how it differs from sibling tools, but the 'Best for' phrase partially addresses this. The low complexity (one parameter) reduces the need for extensive detail.

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 fully documents the single parameter 'question' with a clear description. The tool description adds meaningful context by specifying the types of questions that are appropriate (practical faith, doctrine overviews, life application), which goes beyond the schema's generic 'biblical or theological question' phrasing.

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 purpose: asking a biblical or theological question and receiving a concise pastoral answer with specific characteristics (250-400 words, Reformed theology, Scripture references). It distinguishes itself from sibling tools (e.g., scholar_query, search_sources) by focusing on pastoral and practical answers rather than scholarly or source-based responses.

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 on when to use the tool by specifying it is 'best for practical faith questions, doctrine overviews, and life application.' This implies when to use it, though it does not explicitly mention alternatives or list exclusions, leaving a slight gap in guidance for choosing between this and sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the transparency burden. It states that the tool returns a Scripture reference, verse text, and devotional message, and that it is updated daily, which conveys the core behavior. However, it does not mention potential rate limits, response format details, or explicitly confirm read-only semantics, though the wording strongly implies a safe read operation.

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 sentences, front-loaded with the primary action, and every word adds value. It succinctly covers the tool's function, return content, and update frequency without redundancy or fluff.

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 the tool's low complexity (no inputs, no output schema), the description is complete: it states what is returned and that it is date-specific. The mention of the resource (BEREAN.AI) and the daily update provides sufficient context for an agent to correctly invoke and interpret the result.

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 schema provides complete coverage and the description has no parametric details to add. Per the rubric, a zero-parameter tool earns a baseline of 4, and the description adds no unnecessary parameter information.

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 purpose with a specific verb ('Get') and resource ('today's daily devotion from BEREAN.AI'), and enumerates the return content (Scripture reference, verse text, devotional message). It is unambiguous and distinct from siblings like 'get_daily_exposition' by focusing on 'devotion' rather than 'exposition'.

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 implies when to use it (to retrieve a daily devotion for the current date) but does not explicitly contrast it with sibling tools like 'get_daily_exposition' or state when not to use it. There is no mention of alternatives or exclusions, leaving usage entirely implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It discloses key behavior: returns specific content types and is 'Updated daily.' However, it does not explicitly state that it is a safe, read-only operation or mention potential failure conditions, which would be more transparent for a no-annotation tool.

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 three sentences, front-loaded with the main verb, and each sentence adds value: purpose, contents, and update frequency. No redundant words or filler.

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?

Despite lacking an output schema, the description lists the return components (OT/NT/Psalms/Proverbs references, teaser, commentary) and notes the daily update behavior. This is complete for a zero-parameter retrieval 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?

The input schema has zero parameters, so per the rubric the baseline is 4. The description does not need to explain parameters and correctly avoids doing so, keeping focus on return value.

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 ('today's One Year Bible reading exposition from BEREAN.AI'). It enumerates the returned content (Scripture references, teaser, full exposition), which distinguishes it from sibling tools like get_daily_devotion.

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 implies usage context—'today's' exposition—but does not explicitly contrast with alternatives or state when not to use it. Given sibling tools exist, an explicit distinction would be helpful, but the read-only daily nature is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It discloses the internal retrieval mechanism (dense vector search + cross-encoder reranking), the breadth of sources, and the output format (detailed academic answers with citations). It does not mention potential limitations such as response time, rate limits, or behavior on poor queries, but for a query tool this is reasonably transparent.

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 three sentences, densely packed with useful details (retrieval method, source list, output). Every sentence contributes unique value, and the core purpose is front-loaded. There is no redundancy or fluff.

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 the tool's complexity (large-scale retrieval across many source types), the description covers the essential aspects: what it does, which sources it searches, how it works, and what it returns. With only one parameter and no output schema, it is largely complete, though it could mention how to formulate effective questions or handle cases with no results.

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 single parameter 'question' is already fully described in the schema (100% coverage), so the tool description adds no additional semantics beyond the schema. No examples or formatting guidance are provided, landing at the baseline of 3.

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 purpose with a specific verb ('query') and resource ('academic biblical research'), and provides extensive detail on scope (2M+ passages, lexicons, commentaries, historical texts). It distinguishes itself from siblings by specifying a two-stage retrieval method and source citations, making it distinct from generic 'ask_question'.

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 implies usage for academic biblical research by enumerating the searchable sources and output type. However, it does not explicitly state when to use this over sibling tools like 'ask_question' or 'search_sources', nor does it provide exclusions. The context is clear but lacks direct comparative guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden. It discloses the retrieval mechanism (dense vector retrieval with cross-encoder reranking) and what is returned (raw source passages from lexicons, commentaries, etc.). However, it does not mention result limits, pagination, or explicitly confirm that it is read-only/non-mutating, leaving some behavioral gaps.

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 three sentences, each delivering distinct value: the core function, the technical approach, and the practical use case. It is front-loaded with the primary action and contains no redundant or filler content.

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 single-parameter search tool without an output schema, the description covers the purpose, retrieval method, expected return content, and intended use. It is complete enough for an agent to select and invoke the tool correctly, though it omits explicit return structure or any constraints (e.g., number of results).

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 provides 100% coverage for the single 'query' parameter, including a description. The tool description adds context about returning passages but does not add further semantic detail about query formatting or syntax. Given high schema coverage, 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 opens with 'Search the BEREAN.AI knowledge base directly for relevant passages'—a specific verb, resource, and scope. It also distinguishes itself from sibling tools by explicitly stating 'without generating an AI answer' and 'Returns raw source passages,' making it clear this is for primary-source retrieval, not generative Q&A.

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: use this tool when you need primary source data and do not want an AI-generated answer. It says 'Useful for getting primary source data,' which implies the use case. However, it does not explicitly name alternatives or state when not to use it, so it falls short of the highest bar.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.