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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the bar is lower. The description adds valuable behavioral context: the image field is the raw stored URL (not the computed display), may be null, and 'round-trip[s] with create_collection / add_verse.' It also narrows applicability to 'published collection.'

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 well-structured with a clear summary, a focused paragraph on image behavior, and an Args section. It is slightly verbose for a simple getter, but each sentence serves a purpose—especially the image caveat.

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?

With an output schema present, the description needn't explain return format. It covers what is returned (verse text, references, topics), the image nuance, and the ID source. Combined with rich annotations, this gives a complete picture for an agent.

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%, so the description must compensate. It fully explains the only parameter: 'collection_id: The collection ID (from browse_collections results),' providing both meaning and source. This is sufficient for a single integer 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 uses the specific verb 'Get' with the resource 'published collection' and explicitly states the scope: 'all verse text, references, and topics.' This clearly distinguishes it from sibling tools like browse_collections (list) and get_collection_metrics (metrics).

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 communicates when to use this tool by stating the collection_id comes 'from browse_collections results,' implying a workflow. It also mentions round-tripping with create_collection/add_verse for copying. However, it does not explicitly contrast with get_collection_metrics or 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.