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

Annotations already establish this as a safe, read-only, idempotent operation, so the bar is lower. The description adds useful behavioral context by stating what kind of items are returned and their key fields, going beyond the annotation safety profile. Pagination behavior is not disclosed, but the description still provides meaningful transparency.

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 two concise clauses with the main purpose front-loaded. The parenthetical about sort 'top' earns its place by giving actionable guidance. There is no filler or duplicated schema content.

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?

There is no output schema, so the description should explain the return shape; it partially does by listing author, content, engagement, and engagementScore. However, it does not mention pagination behavior, default limits, or how page/limit affect results, which are important for a browse tool with these parameters.

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 only 60%, with page and limit left undocumented. The description's only parameter-related addition is the sort 'top' engagement guidance, which largely restates the schema's own 'top = highest engagement first.' It does not compensate for the missing page and limit semantics.

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: 'Browse the mined content in a collection', then names exact item types (posts/comments/profiles) and the returned fields (author, content, engagement, engagementScore). This clearly distinguishes the tool from collection-level siblings like neuron_get_collection and neuron_list_collections.

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 provides a concrete usage context by explaining that sort 'top' ranks by engagement and is 'great for picking the best clips/posts to reuse or distill into a persona.' It does not explicitly name alternative tools or when-not conditions, but the intended scenario is clear.

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