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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful behavioral context: it specifies the exact output fields (title, summary, public Markdown teaser, sources) and the limitation that the full body is not returned.

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 two sentences with no redundancy. The main action and scope are front-loaded, followed by the return-value list and the subscription limitation. Each clause contributes to the agent's understanding.

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 simple listing tool with one optional enum parameter and no output schema, the description covers what the tool returns and what it does not return. Minor gaps such as pagination, ordering, or filtering are not critical here, so completeness is slightly above average.

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 the single locale parameter is fully documented with enum values and a default. The description adds no parameter-level information, so the baseline score of 3 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 states a specific action ('Lista os Estudos publicados') and clearly identifies the resource and scope: published Studies with patakí retellings cited by edition/page or exact myth title, in two tracks (Odu and Orixá). It also lists the returned fields, making it easy to distinguish from siblings like get_article or list_articles.

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?

The description explicitly says the full body is for subscribers and not available through this tool, which implicitly frames it as a metadata-only listing tool. However, it does not name alternatives for full-body access or state when to prefer this over list_articles or search_library.

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