Blogs List

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely useful context beyond them: the required read_content scope, the API version, and the pagination envelope returned. The only gap is it doesn't state filtering/sorting behavior, which for a plain list is minor.

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?

Extremely compact and front-loaded: the purpose sentence comes first, followed by endpoint, scope, version, and return shape in that order. The terse field-list style is efficient rather than wasteful, though the return-shape line is somewhat notation-dense.

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?

For a simple read-only list tool with no output schema, the description supplies the missing pieces an agent needs – auth scope, API version, and the exact response envelope including pagination fields. It stops short of 5 only because the relationship to blog posts endpoints is unaddressed.

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 page, per_page, fields, and response_format are already fully documented in the schema. The description adds nothing about parameter semantics, which is the baseline-3 case when the schema carries the load.

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 ('List blogs of the store'), which an agent can immediately map to the blogs collection. It does not explicitly contrast with the nearest sibling tiendanube_blog_posts_list, so the list-blogs vs list-posts distinction must be inferred from the names.

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?

Usage is implied by 'List blogs of the store' – an agent can reasonably infer this is the read operation for blogs – but there is no explicit statement of when to use it instead of tiendanube_blog_posts_list or which prerequisites must hold beyond the scope line.

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