SearchObject

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

Tags the tool as [read-only] at the start, which is appropriate. No additional behavioral details (e.g., side effects, auth) are needed for a search tool, but the description does not elaborate beyond the label.

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 a single paragraph that front-loads the purpose and is concise, though it could be slightly shorter without losing meaning. No unnecessary repetition.

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 tool's simplicity with 3 parameters and no output schema, the description adequately covers purpose, usage, and parameter semantics. It omits return format, but that is acceptable.

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 baseline is 3. The description adds value by explaining wildcard patterns, listing example object types, and clarifying the maxResults default, going beyond the schema descriptions.

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's function: searching for ABAP repository objects by name or wildcard pattern, with examples of questions and object types. It distinguishes itself from sibling CRUD tools.

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?

Provides explicit usage scenarios ('Use this tool to answer questions like...') and mentions optional filtering by type. Lacks explicit when-not-to-use or alternative tools, but context with siblings implies this is the search tool.

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