Install SAP MCP Skills

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

Beyond the confirm requirement, the description does not disclose behavioral traits such as whether existing files are overwritten, directory creation, or permissions needed. Annotations do not contradict but offer no additional context.

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 extremely concise at two sentences, front-loading the action with no unnecessary words.

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 is adequate for a simple installation tool but lacks details such as what 'bundled SAP MCP skills' are, the default target directory, and the return value (though an output schema exists but is not shown).

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?

All parameters have schema descriptions (100% coverage), so the baseline is 3. The tool description does not add extra meaning beyond what the schema provides, but that is acceptable per guidelines.

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 action ('Install bundled SAP MCP skills into a local agent skill directory') and the resource, distinguishing it from sibling tools like sap_skills_bundle and sap_skills_list.

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 only mentions a requirement ('Requires confirm: true') but provides no guidance on when to use this tool versus alternatives like sap_skills_bundle or sap_skills_list.

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