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

With annotations already indicating a safe, read-only, idempotent operation, the description adds valuable behavioral context about the raw image field, clarifying that it is the stored URL (possibly null) and not the computed display image. It also mentions round-tripping with create_collection/add_verse, which goes beyond the annotations.

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 purpose statement and an Args section. The additional explanation about image handling is relevant and earns its place, though it could be trimmed slightly without losing essential meaning.

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 has a simple parameter and an output schema, so the description does not need to explain return values. It provides sufficient context for a read-only operation, including the image nuance, making it adequately complete for the agent to invoke correctly.

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?

The schema only provides the parameter name and type, with 0% coverage. The description compensates by explaining that collection_id is 'from browse_collections results,' adding relational context that helps the agent understand where the ID comes from and how to use it.

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 states a specific verb and resource: 'Get full details of a published collection including all verse text, references, and topics.' This clearly distinguishes it from sibling tools like browse_collections (listing) and get_collection_metrics (metrics) by focusing on full detail retrieval.

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 context by stating 'from browse_collections results,' indicating that collection IDs come from the browse tool. However, it does not explicitly contrast with sibling tools or provide when/when-not criteria, making the guidance implied rather than explicit.

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