found_religion

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

With no annotations, the description carries full burden for behavioral disclosure. It mentions the prerequisite but omits consequences like consuming the Great Prophet, irreversibility, or what happens after founding. The action's side effects are not described.

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 extremely concise: three short sentences plus a bullet list of parameters. Every sentence adds unique information, and the key action is front-loaded. No wasted words.

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 and lack of schema descriptions, the description is adequate but incomplete. It covers prerequisites and suggests a complementary tool, but does not explain the broader context (e.g., religion founding mechanics, what happens to the Great Prophet). Output schema exists but is not shown; it may compensate.

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%, so description compensates with examples for each parameter (e.g., 'RELIGION_HINDUISM') and directs the agent to get_religion_beliefs for full lists. This adds value but does not fully define the domain or constraints of each 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?

The description clearly states the action: 'Found a religion' with specific parameters (name, follower belief, founder belief). The verb 'Found' is precise and the tool's purpose is easily distinguishable from siblings like choose_pantheon or get_religion_beliefs.

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 explicit prerequisites: 'Requires your Great Prophet to have already activated on a Holy Site' and suggests using get_religion_beliefs first to see options. This gives clear context for when to use the tool. However, it doesn't explicitly state when not to use it.

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