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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: webhook-feed collections additionally expose the ingest URL and POST-signing instructions, while the secret is never printed — an important disclosure about output sensitivity.

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?

Two sentences, zero filler, with the core read purpose front-loaded and the webhook caveat as a secondary clause. Every sentence carries information.

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 no output schema, the description usefully previews the returned fields and the conditional webhook payload. It does not cover lookup failure behavior (what happens on an unknown slug) or confirm site scoping, which a read-by-slug tool would benefit from.

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 coverage is 100%, with both id and slug documented in-schema, so the baseline is 3. The description says 'one collection' but does not clarify slug-vs-id selection or that only slug is required, adding nothing 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?

States a specific verb and resource ('Read one collection's definition') and enumerates what comes back (schema fields, source, isPublic). A single-collection read is clearly distinguished from list_collections and update_collection_schema in the sibling set.

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 'one collection' framing implies this is the single-item read rather than the list, but no sibling is named and no condition (e.g., 'after list_collections to inspect a schema') is given. Usage is inferable but never stated.

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