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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful trait beyond the annotations — results are ranked 'best match first' — but the remaining sentence is marketing copy about the corpus, not 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?

The first fragment is clear, but the trailing run-on sentence ('daily readings from Marcus Aurelius, Epictetus and Seneca explained line by line, plans, search, and the whole Meditations...') is an unstructured content catalog that pads the definition without helping selection or invocation.

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 one-parameter read-only search with full annotation coverage and no output schema, the essentials are present, and 'best match first' hints at ranking. It still omits match semantics (which fields are searched) and any result-count or pagination expectations.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains the free-text query and even supplies examples ('anger or death'). The description adds nothing about how the query is matched (keyword vs semantic), so the baseline 3 applies.

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 ('Search the curated readings') and even specifies result ordering ('best match first'). However, it never distinguishes this from close siblings such as stoics_list_readings or stoics_get_reading, so an agent must infer the search-vs-list-vs-fetch boundary on its own.

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 when-to-use guidance is given. There is no mention of when to prefer this over stoics_list_readings, stoics_read_book, or stoics_get_reading, and no prerequisite or query-shaping advice. Usage must be entirely inferred from the tool name.

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