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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description is consistent with a safe read operation. It adds meaningful behavioral context beyond annotations: the level field is sparse, null means 'not graded' rather than 'Beginner', category counts can drift, and the live envelope should be trusted over prose.

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 description is longer than minimal, but each sentence earns its place by adding operational context. It is front-loaded with purpose and return fields, then moves through caveats and sibling routing. The category paragraph is dense and somewhat convoluted, but the structure is logical and not wasteful.

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 read-only search tool with a rich schema and output schema, the description covers all important context: return fields, null semantics, pagination envelope behavior, category vocabulary drift, and when to use sibling tools. Nothing critical is missing for an agent to invoke it correctly.

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 100%, so the baseline is 3. The description adds value beyond the schema by explaining level null semantics, emphasizing that category labels are long human labels and not to be guessed, and pointing to the always-returned _meta.available_categories. Cursor and query semantics are already well documented in the schema.

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 opens with a specific verb and resource — search the SAP analytics concept encyclopaedia — and enumerates the exact returned fields: slug, title, category, level, tags, and the editor's summary. It also explicitly distinguishes itself from get_concept and get_concept_card, making its purpose unambiguous.

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 gives clear routing guidance: get_concept returns the same fields for one slug, while get_concept_card should be used for the body content. It also explains practical search semantics and warns against guessing category labels, telling the agent to rely on the live _meta.available_categories envelope instead.

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