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

Annotations declare readOnlyHint=true and destructiveHint=false, which is consistent. The description adds valuable behavioral details: admin vs. normal user visibility (draft/published vs. published only), case-insensitive matching, and a canonical URL in results. No contradictions with annotations.

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, one focused on function and the other on role-based behavior and usage hint. No wasted words, front-loaded with the core action.

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?

Given the presence of an output schema, the description covers purpose, parameter semantics, role-based behavior, and duplicate avoidance. For a search tool with a few parameters, this is complete and actionable.

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 33% (locale has description). The description compensates by explaining that query accepts multiple term types (English, Arabic, abbreviation, slug) and that locale is the caller's language, ignored for admins. This adds meaning beyond the bare schema for two of three parameters.

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 clearly states it searches terminology by English term, Arabic term, abbreviation, or slug using normalized case-insensitive matching. It distinguishes this tool from siblings (news, explainers, server status) by specifying the exact resource and search fields.

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 description advises administrators to call before creating a new term to avoid duplicates, and notes that other accounts see only published terms and must pass the caller's locale. It does not explicitly state when not to use, but provides clear context for different user roles.

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