blogs_get_blogs

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond restating the location ID parameter that is already in the schema. It doesn't mention pagination behavior, whether results are ordered, or what happens with the searchTerm field. Thus, it provides minimal additional behavioral context beyond the annotations.

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, concise sentence with no redundancy. However, it is so brief that it omits essential information about behavior and parameters, but the conciseness itself is acceptable, similar to the example of 'update_drive' which scored 4.

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 list endpoint with four parameters including pagination and search, this description is inadequate. It doesn't mention what the response contains (no output schema exists), how pagination works, or the role of searchTerm. An agent would struggle to know what to expect or how to properly use the tool.

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 50%, with skip and limit lacking descriptions. The description only mentions locationId, which already has a schema description. It doesn't explain how skip/limit control pagination or how searchTerm affects results. The description fails to compensate for the schema gaps.

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 states a clear verb+resource combination: 'Get Blogs by Location ID'. It suggests retrieving blogs filtered by a location, which is reasonably specific. However, it doesn't clarify whether it returns a list or a single blog, though the presence of pagination parameters (skip, limit) implies a list. The sibling tool blogs_get_blog_post exists, so this likely retrieves all blogs for a location, but that distinction isn't explicit.

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?

There is no guidance on when to use this tool versus alternatives like blogs_get_blog_post, blogs_create_blog_post, or other blog-related tools. The description provides no context about scenarios where filtering by location is appropriate or when other tools should be preferred.

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