blogs_check_url_slug_exists

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, which cover safety and idempotency. However, the description adds no additional behavioral context—such as the return format (likely boolean), behavior when slug is found vs. not, or any location scope. It does not contradict annotations but also provides no extra 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 extremely concise (three words) but this is under-specification, not efficient succinctness. It front-loads nothing useful and provides no structure that aids an agent in understanding the tool.

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 no output schema, 3 params with minimal descriptions, and a vague one-line description, the tool is not adequately described. An agent cannot confidently know what this tool does, what it returns, or how to call it correctly without additional context.

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 coverage is only 33% (only locationId has a description), and the description itself adds no meaning to any parameter. It does not explain the purpose of postId (likely to exclude a post when checking uniqueness) or the required urlSlug beyond being the subject. The description utterly fails to compensate for the sparse schema documentation.

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 'Check url slug' is a near-tautology of the tool name 'blogs_check_url_slug_exists' and does not clarify whether 'check' means existence, availability, or format validation. It specifies a verb and resource but is too vague to distinguish from potential alternatives or to convey the actual intent (e.g., returns true/false if slug exists).

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?

No guidance is provided on when to use this tool, under what circumstances (e.g., before creating a blog post to verify uniqueness), or what alternatives exist. The description lacks any contextual cues or exclusions.

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