SAPManage

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

Annotations indicate destructive potential, and the description adds important context: mutations require writable safety config and write scope. It also warns that 'available: false' means not to attempt dependent operations. This goes beyond the annotation flag to explain the behavior.

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 front-loaded with a clear purpose sentence and then organized into bullet-point actions. It is reasonably concise given the number of actions (12), but some internal repetition exists (e.g., mentioning return values only for feature actions). Overall well-structured.

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 tool has 20 parameters and no output schema. The description explains return format only for the feature-probe actions (features, probe, cache_stats). For the other nine actions (mutations and FLP queries), no return type or expected response is provided. This leaves the agent unaware of what to expect after creation or deletion. Error handling and prerequisites (beyond writable config) are also absent.

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?

With 100% schema coverage, the baseline is 3. The description adds value by grouping parameters by action and indicating which are required for specific actions (e.g., catalogId for flp_list_tiles). This helps an agent understand parameter usage context beyond individual 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 dual role: probing SAP system capabilities and managing package/FLP lifecycle. It distinguishes from sibling tools like SAPRead and SAPSearch by emphasizing proactive probing before dependent operations. The verb 'Manage' is appropriately reflected in the listed actions.

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 using this tool before operations that depend on optional features, providing a clear use case. However, it does not explicitly state when not to use it or compare to siblings for read-only package queries. The guidance is strong but could be more exhaustive.

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