find_tools

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It warns that most tools are deferred and that the 'enable' parameter defaults to true, but does not elaborate on side effects of enabling, rate limits, or idempotency. This is adequate but not rich.

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 front-loads the core purpose and warning, then lists categories concisely within a single paragraph. While the category list is somewhat lengthy, it is necessary for clarity. No redundant content.

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 explains the tool's purpose and behavior well, including the deferred nature and enablement. However, it lacks information about return values (no output schema) and what happens if tools are already enabled or if enable is false. Adequate but not comprehensive.

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 description coverage is 100%, so the description only adds marginal value beyond the schema. It mentions categories and implies search by name/description, but does not detail parameter usage or format needs. Baseline of 3 is appropriate.

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 finds and enables ABAP tools by search term or category, with a specific warning about deferred tools. It distinguishes from siblings like list_tools by explaining its role as a prerequisite for non-core tool usage.

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 explicitly advises calling this tool before using any non-core tool, provides a comprehensive list of categories, and notes that enabled tools become immediately available. It could further clarify when not to use it or contrast with sibling tools, but the guidance is effective.

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