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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuine context beyond that: results are read from Firestore at call time, i.e., fresh/live rather than cached. It does not disclose result limits, ordering, or what happens with an empty query or unmatched terms, which matters for a tool with zero required parameters.

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 sentences, both front-loaded: the verb and scope lead, and the freshness caveat follows. The enumerated domain list is long but each item is a real capability, so it earns its space. Slightly list-heavy, but no filler sentences or marketing language.

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?

An output schema exists and annotations are rich, so the description need not explain return values or safety. What it does cover — searchable domains and live-data freshness — is the right material. The missing piece is routing: with 14 siblings including several near-overlapping getters, the description should say when this broad search beats a targeted sibling call, and it does not.

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%, so the baseline is 3. The description adds nothing about parameter behavior — it does not mention the q/query alias pair or explain how query intent maps onto the enumerated domains. It neither helps nor compensates beyond what the schema already provides.

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 (Searches) and resource (the user's live Lingard account), and enumerates the searchable domains: vocabulary, learning context, profile, totals, collections, saved words, flashcards, missing fields. This is far more than a restatement of the name. However, it does not differentiate itself from siblings that cover the same ground (e.g., lingard_get_learning_context, lingard_get_vocab_collection), so the agent cannot tell from the description alone whether this generic tool or a specific one is correct.

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?

There is no when-to-use or when-not-to-use guidance, and no named alternatives. The enumeration of searchable domains implies broad usage, but several siblings (lingard_get_learning_context, lingard_get_vocab_collection) appear to overlap directly, and nothing tells the agent which to prefer. The agent must infer routing from sibling names it may not have read.

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