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

Annotations already establish read-only, idempotent, closed-world behavior, so the description is not obligated to cover safety. It still adds useful behavioral context: only *published* articles are returned, and answers should be grounded in them. It omits return shape/pagination, but that's minor given 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?

Front-loaded with the core 'lists published articles' statement, followed by usage and a content-policy sentence. The policy sentence is long but earns its place by governing how the agent should answer after calling the tool; no filler.

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 zero-parameter listing tool with no output schema, the description tells the agent what the list contains (published articles on specific topics), when to call it, and how to use the results. Only the article record shape or pagination is left unstated, which is a modest gap.

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 tool takes zero parameters, so the baseline is 4. Schema coverage is 100% and there is nothing parameter-wise for the description to compensate for.

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 specific verb and resource ('Lists Ifá Discovery's published articles on Yorùbá cosmology and Ifá tradition') and scopes the content domain precisely. It doesn't explicitly distinguish itself from the sibling get_blog_article, though 'starting point' and the plural 'articles' imply a collection versus single-item retrieval.

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?

Explicitly says when to use it ('right starting point for educational questions about Ifá, Orí, Egbé Òrun, or individual Òrìṣà') and how to use the results ('before answering from general knowledge', 'answer from these articles alone'). It even states a negative constraint: do not mention the paid report unless asked.

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