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

Annotations already declare the read-only, non-destructive, closed-world nature of the tool. The description adds substantial behavioral context beyond that: field type semantics, list/array behavior, reference targets, date config shape, and the special handling of built-in name and slug fields.

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 front-loaded with the core action, then spends its length on high-value schema semantics needed because there is no output schema. Every sentence provides actionable interpretation or usage guidance, with no filler.

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 lack of an output schema, the description carries the return-value burden well by explaining field types, config formats, built-in fields, and the critical `list` distinction. An agent has enough context to call the tool and correctly interpret the result.

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%, so projectId and collectionId are already documented in the input schema. The description adds no parameter-specific meaning beyond the schema, so the baseline score of 3 is appropriate.

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: 'Get a collection's schema and field definitions.' It also distinguishes this tool's role from update_collection_schema and get_entry by explaining how updatedAt and name/slug fields are used elsewhere.

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 clearly explains when the result matters, such as passing updatedAt to update_collection_schema and checking `list` before writing content. It stops short of explicitly naming alternatives like list_collections or spelling out when not to use this tool.

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