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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description adds substantial behavioral context beyond that: the 10-item limit, reverse chronological ordering, absence of pagination, and the fact that it returns only compact metadata and excerpts. This gives an agent an accurate model of the tool's effects and output character.

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 efficient sentences with no filler. The core capability and limit are front-loaded in the first sentence, the bounded nature and return style in the second, and the follow-up routing in the third. Every sentence earns its place.

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?

The tool is simple (one optional parameter) and has both an output schema and rich annotations. The description covers ordering, limit, filtering, return style, pagination behavior, and the path to full sermon text via get_sermon. Nothing an agent needs to decide whether to call it is missing.

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 100%; the schema already explains camera_id as an optional stable public church profile ID and tells the agent to omit it to list all churches. The description only paraphrases 'optionally limited to one church', adding no semantic information beyond the schema.

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 a specific verb and resource: 'List up to 10 latest public sermons from msza.ai in reverse chronological order'. It adds scoping details (optional church filter) and distinguishes itself from siblings by calling itself a bounded discovery tool and pointing to get_sermon for full text, so an agent can tell it apart.

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?

It explicitly states when to use the tool (bounded discovery with no pagination, compact metadata) and when not to: 'Use get_sermon with a returned session_id when full sermon text is needed.' It also explains the behavior when camera_id is omitted, giving clear context for the single optional parameter.

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