Find SAP Tools By Category

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

The description claims the tool is a 'Read-only SAP SDK wrapper', but the annotations set readOnlyHint to false, creating a direct contradiction. This undermines the agent's understanding of the tool's side effects.

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 very concise at two sentences, with no unnecessary words. The first sentence states the core function, and the second provides useful context.

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 is insufficient due to the behavioral contradiction, and it omits details like pagination behavior (limit parameter) or how the output is structured. Given that an output schema exists, this is partially mitigated, but the contradiction is a significant flaw.

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?

All three parameters are fully described in the schema (100% coverage), so the description does not need to add further meaning. However, it adds no extra context beyond the schema, such as expected values for the category parameter.

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?

Description clearly states the tool finds tool descriptors by category name or numeric ID, and specifies it is a read-only operation. However, it does not explicitly differentiate from sibling tools like sap_get_tool_category_summary, which may have a related purpose.

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 using this tool for inspecting chain state before mutations, providing context for when to use it. However, it does not specify when not to use it or point to alternative tools for different needs.

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