blogs_get_all_blog_authors_by_location

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. However, the description adds no behavioral context beyond that, such as the fact that results are paginated via limit/offset, that a default location applies, or that the response is a list. It is a bare statement that provides no additional 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 only four words, which is extremely concise but not appropriately sized. It omits critical context (e.g., what is being listed, scoping) and does not front-load the key distinction. While it has no waste, it is under-specified to the point of being unhelpful.

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 the tool has three parameters, no output schema, and only terse annotations, the description should explain that this retrieves a paginated list of blog authors for a location, possibly with default behavior. It lacks this context, making it incomplete for an agent to understand what the tool does beyond the name.

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%, and each parameter (limit, offset, locationId) already has a clear description in the schema. The description adds no additional semantic meaning about parameters. Per the rubric, baseline is 3 when coverage is high, so this score 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 'Get all authors' is vague and underspecified. It does not indicate that these are blog authors, nor that the results are scoped by location. The tool name carries the specificity, but the description itself could apply to any author entity. It is nearly a tautology of the name and fails to differentiate from siblings like blogs_get_all_categories_by_location.

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. The description does not mention pagination, default location behavior, or when this tool is preferred over other blog-related or author-related tools. An agent receives no context about typical usage scenarios or prerequisites.

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