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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, indicating safe, idempotent read behavior. The description adds pagination details and filtering capabilities, which are consistent with the annotations. No contradictions.

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 a single sentence with 18 words, front-loading the main action and key features. Every word conveys necessary information; no redundancy or fluff.

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 6 optional parameters, pagination, and two enums, the description captures the essential behavior concisely. However, it does not describe the response format (e.g., list of posts with pagination metadata), which would be helpful since no output schema is provided. Still, for a simple list tool, it is fairly complete.

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 description coverage is 100%, with each parameter documented in the schema. The description adds overall context ('paginated list', 'optional filtering') but does not provide additional meaning beyond the schema definitions. Baseline 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 clearly states the verb 'Retrieve' and the resource 'list of blog posts', with specific filtering options (status, author type, author ID, tag) and pagination. It distinguishes itself from sibling tools like neuron_get_blog_post (single post) and neuron_create_blog_post (creation).

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 does not explicitly state when to use this tool versus alternatives such as neuron_get_blog_post for a single post or neuron_publish_blog_post for changing status. The 'optional filtering' implies some use cases but lacks clear guidance on when to choose this over others.

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