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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful shape information — two distinct response modes depending on the concept parameter, and that cards come back as excerpts with a link — but says nothing about missing keys, unknown slugs, or result size.

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?

Two dense sentences with no filler; the primary fetch is front-loaded and the conditional concept mode follows. The clause "what the term means, what it does in this maamar, and the deeper point" is a slightly listy run-on but each element carries information about the return value.

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?

With no output schema, the description must convey return values and does: parts, concept cards, and the excerpt-plus-link card payload. For a read-only lookup with fully documented parameters, the remaining gap (what a "part" looks like, error behavior) is minor.

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 100%, so the baseline is 3, but the description goes beyond it: it identifies book and maamar as keys sourced from list_in_depth, and it explains what supplying a concept key actually yields rather than merely calling it "optional". The language fallback behavior is left entirely to the schema.

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 resource (one In Depth maamar identified by book + maamar slug) and what it returns (its parts and concept cards), plus the conditional mode when a concept key is supplied. It routes the agent to list_in_depth for the keys, though it does not distinguish itself from get_topic, which also deals with concepts.

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?

"from list_in_depth" tells the agent where the required keys come from, and "With a concept key, that card" clearly states the optional second mode. There is no explicit when-not-to-use guidance or named alternative for retrieving a concept outside a specific maamar (e.g. get_topic).

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