btp_execute_command

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

Mentions automatic JSON formatting and error detection, but does not disclose what happens on failure, return format, security/authentication requirements, or any rate limits. With no annotations, more behavioral context would be helpful.

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?

Three concise sentences, front-loaded with purpose, guidance, and a safety note. No fluff, but could be slightly more structured (e.g., bullet points) for easier scanning.

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?

Lacks explanation of return value or output format. Given the tool is a generic fallback, more details on expected output, error handling, and edge cases would be needed for complete understanding.

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?

Neither the input schema nor the description explain what 'args' and 'kwargs' mean. Both are required strings, but the agent has no guidance on how to structure them. The description does not compensate for the 0% schema description coverage.

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?

Clearly states it is a generic execution engine for ANY SAP BTP CLI command. Explicitly distinguishes from sibling tools by saying to use it only when a dedicated tool is not available.

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 guidance: 'Use this if a dedicated tool is not available for a specific resource type.' This tells the agent when to invoke this tool vs its siblings.

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