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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds that it is a 'Free local tool' and uses 'FTS5' full-text search, but does not elaborate on performance limits, output format, or other behavioral aspects beyond what annotations cover.

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 somewhat concise but contains a second paragraph of SAP-specific execution guidance that may be irrelevant or verbose for most agents. It could be more streamlined.

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 6 parameters, annotations, and presence of an output schema, the description is adequate but not complete. It lacks details about default sorting, pagination behavior, or the structure of search results, relying on the schema to fill in gaps.

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 input schema has 100% description coverage for all 6 parameters, so the schema already provides necessary meaning. The description does not add any additional semantic value for parameters beyond what is 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 clearly states it performs full-text search across tool call history. The specific verb 'search' and resource 'tool call history' are present. However, the inclusion of SAP-specific execution guidance may distract from the core 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 gives a use case ('Find patterns, failures, and successes') and mentions 'Intent: read/discovery workflow', but does not explicitly differentiate this tool from similar siblings like sap_memory_recall. No when-not-to-use guidance is provided.

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