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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered structurally. The description contributes the ranking behavior ("best-matching"), but says nothing about how matches are scored, whether results are truncated, or how the limit interacts with the returned page set.

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?

A single sentence with zero filler that front-loads the verb and the resource. It is efficient, though its brevity leaves no room for the usage or limit context an agent needs.

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 carries the burden of explaining the return shape, yet it only says "best-matching pages." Combined with an undocumented limit parameter, an agent cannot tell whether results are ranked, how many come back by default, or whether a follow-up fetch is needed.

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 only 50%: the query parameter is documented in the schema, but limit (default 8, max 25) has no schema description at all. The description never mentions limit or result-set sizing, so it does not compensate for the coverage gap.

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 the Mammoth Analytics docs") plus the outcome ("return the best-matching pages"), which distinguishes it from a direct get_doc fetch. It does not explicitly name the siblings get_doc or list_docs, so the differentiation is implied rather than stated.

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 phrase "best-matching pages" implies relevance-ranked lookup when you don't already know the document, which is the natural complement to get_doc. However, there is no explicit when-to-use or when-not-to-use statement and no named alternative, leaving the agent to infer routing between search_docs, get_doc, and list_docs.

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