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

Annotations already establish readOnly/idempotent/non-destructive, so the description's job is to add context — which it does by disclosing the pre-built index (no downloads), the absence of scope filtering, the exact return shape, and the chronological sort behavior. It doesn't discuss result-set size limits or how absence/misses surface beyond the naming heuristic, so it falls slightly short of full behavioral coverage.

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?

Purpose is front-loaded, the bilingual heading is compact, and the workflow plus examples are ordered sensibly. It loses a point for redundancy: 'No scope (authors aren't scoped by category/period)' appears both in the body and verbatim inside the options description.

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 5-parameter nested-object search with no output schema, the description covers what is searched, what is returned, the sort semantics, the naming-variant edge case, and the next tool to call — while annotations carry the safety profile. Nothing an agent needs to call it correctly is missing.

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%, with limit/offset/options fully documented in the schema, so the baseline is 3. The description reinforces options.sort ('chronological' orders by death year, earliest first) and demonstrates options.wildcards in an example, but adds no parameter detail the schema lacks.

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?

States a specific verb and resource ('Search Shamela's ~3,200-author catalog by name or biography text'), names the return fields (author name, Hijri death year, book count), and differentiates itself from the page/book search siblings by noting authors carry no category/period scope. An agent can tell exactly what this tool does without opening the schema.

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 routes the agent downstream: use the resulting author_id with shamela_get_author for details, or with scope.author_ids in shamela_search_pages/_books. It also gives a concrete recovery heuristic for misses (try kunya, nisba, shuhra variants before concluding absence) and two runnable examples.

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