listBlogs

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. The description says nothing about read-only nature, pagination, rate limits, or any side effects. The input schema hints at pagination via limit and cursor, but the description fails to explain this behavior.

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?

At only two words, the description is under-specified rather than concise. It does not earn its place, as it provides no value beyond the tool name. A concise description should still convey essential context; this falls short.

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 absence of annotations, output schema, and parameter descriptions, the description is severely incomplete for a tool with 2 parameters and numerous sibling tools. The agent lacks information on pagination, return format, and when to use this 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?

The input schema has 0% description coverage for its parameters, and the description adds no information about limit or cursor. The agent receives no additional meaning beyond the schema's type definitions. The description must compensate for low schema coverage but does not.

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 'List blogs' specifies a verb and resource, making it clear what the tool does. However, it is extremely brief and does not differentiate from numerous sibling list tools like listProducts, listOrders, or listCustomers. A score of 3 reflects adequate clarity but lacks distinguishing context.

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 versus alternatives. The description does not mention any conditions, exclusions, or comparisons to sibling tools that also list resources. This omission leaves the agent with no direction on selecting this tool over others.

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