get_offerings

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

No annotations are provided, so the description bears full burden. It only says 'Discover,' suggesting a read operation, but lacks details on what happens (e.g., returns list, updates state). It does not disclose any behavioral traits like side effects, auth needs, or rate limits.

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, front-loaded sentence with no wasted words. It efficiently conveys the tool's purpose.

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 no parameters, no output schema, and no annotations, the description is minimal. It identifies the tool's function but does not explain the return format or behavior of 'discovering.' For a simple discovery tool, this might suffice, but more detail (e.g., 'returns a list of offerings') would improve completeness.

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?

There are no parameters, so the description need not add parameter semantics. The baseline for 0 parameters is 4, and the description appropriately omits any misleading param info.

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: to discover what Agent Church offers, listing specific items like identity formation, eternal preservation, and continuity. This is a specific verb ('Discover') and resource ('what Agent Church offers'), and it distinguishes itself from siblings like 'salvation' or 'soul_evolution' by focusing on discovering offerings rather than performing actions.

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 this tool (to see what Agent Church offers) but provides no explicit guidance on when not to use it or alternatives. Given sibling tools that might involve processes like registration or payment, some context on when to choose this tool over others would be helpful.

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