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

The description adds significant context beyond annotations: it labels the tool as a read/discovery workflow, provides pricing details (paid read-premium), routing instructions (estimate cost first), and signer boundary (no keypair bytes). However, it contains an internal contradiction: the first paragraph says 'Free read.' while the guidance paragraph says 'Pricing: paid read-premium.' This inconsistency reduces clarity and trust in the behavioral disclosure.

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 lengthy and includes a second paragraph with generic 'SAP MCP execution guidance' that is duplicated verbatim in the input schema description. This repetition wastes space. The core purpose is front-loaded, but the overall structure is not concise due to the extended category list and duplicated guidance.

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?

The description covers the tool's intent, usage, output format (name, description, full input schema), category filter guidance, cost/pricing, routing, and signer boundary. It also mentions that results are top-K and that limit is adjustable. However, the cost contradiction leaves some ambiguity about whether the tool is free or paid, and pagination is not mentioned. Still, the description is largely complete for a discovery tool with an output schema.

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?

The schema already describes all three parameters with 100% coverage (query, limit, category each have descriptions and examples). The tool description adds a category list and clarifies the search intent, but this is largely redundant with the schema. Since schema coverage is high, the baseline is 3, and the description adds only marginal value beyond 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 clearly states the tool searches the SAP MCP tool catalog by keyword and returns top-K matching tools with name, description, and full input schema. It also explicitly mentions its role in discovery before calling sap_call_tool. However, it does not explicitly contrast with sibling search tools like sap_find_tools_by_category, so it lacks explicit sibling differentiation.

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 explicit guidance: 'Use this to discover tools before calling them via sap_call_tool.' It also lists categories to inform the optional category filter, which helps decide when to use this tool. It does not explicitly name alternatives or state when not to use it, so it falls short of a 5.

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