SAPManage

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

With no annotations, the description carries the full burden for behavioral disclosure. It details that features action is cached and fast, while probe performs a round-trip with auth checks. It also warns when operations should not be attempted based on feature availability. However, it omits behavioral details for package operations (e.g., prerequisites, side effects) and does not mention rate limits or potential destructive actions.

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 well-structured with a clear opening statement, an action list, and return format details. However, it is somewhat verbose, especially the actions list which could be condensed. The front-loading of purpose is effective, but the length slightly detracts from conciseness.

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 covers the probing aspect well, including return format and when not to use features. However, for package operations (create, delete, change_package), it does not describe the return values, error behavior, or any side effects. Given the tool's complexity (19 parameters, multiple domains), this omission leaves significant gaps for the agent.

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?

Parameter schema coverage is 100%, so the baseline is 3. The description adds value by grouping parameters under each action in the bullet list, making it clear which parameters are required for specific actions. This contextual grouping helps the agent select the right parameters beyond the flat schema list.

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 purpose: probing SAP system capabilities and handling package (DEVC) lifecycle operations. It uses specific verbs ('probe', 'report', 'handles') and distinguishes itself implicitly by advising use before operations that depend on optional features, which sets it apart from sibling tools that likely handle other tasks like reading or searching.

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 provides clear guidance on when to use the probe action ('on first use or if feature availability changed') and states the overall pre-check intent ('Use this BEFORE attempting operations that depend on optional features'). However, it does not explicitly mention when not to use the tool or compare it directly with siblings like SAPTransport or SAPRead, which slightly limits its completeness.

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