character_profile

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

Annotations already declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds that it returns verses, which is consistent, but provides no additional behavioral context such as rate limits, error handling, or what happens for non-existent characters.

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, focused sentence with no fluff. It immediately conveys the core functionality and a key differentiator.

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 that an output schema exists, the description doesn't need to detail return format. However, it omits how the tool handles ambiguous names, or how it selects verses (e.g., by direct mention or broader association). This leaves gaps for an AI agent to resolve, especially alongside similar sibling tools.

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 description coverage is 0% for parameters, meaning the schema itself lacks meaningful descriptions. The tool description does not mention any parameter details (name, limit, translation) or how they affect results, forcing the agent to infer from parameter names and constraints.

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 returns verses about a biblical character and explicitly distinguishes itself from a curated biography database. This verb+resource combination is specific and differentiates from sibling tools like search_verse or get_verse.

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 retrieving raw verses rather than biography, but it does not explicitly state when to use this tool versus alternatives like search_verse or topic_lookup. No exclusions or when-not-to-use guidance is provided.

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