Show SAP MCP Profile Agent Public Key

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

The description states the tool returns a public key without reading or exposing keypair bytes, suggesting a read operation. However, the annotation readOnlyHint is false, which contradicts this. This discrepancy reduces transparency significantly.

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 a single, focused sentence that front-loads the purpose and adds a security-relevant qualifier. No wasted 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?

For a simple tool with an output schema, the description is minimally adequate. However, it lacks guidance on when to use it and does not resolve the annotation contradiction, which could confuse 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?

Schema coverage is 100% (one parameter fully described in schema). The description adds no additional meaning beyond the schema's description of the parameter.

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 purpose: returning the configured public agent key for a profile. The verb 'Return' and the resource 'public agent key for a profile' are specific, and the additional clause 'without reading or exposing keypair bytes' distinguishes it from other sap tools that might expose more sensitive data.

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 no explicit guidance on when to use this tool versus alternatives. It implies the tool is for retrieving public keys, but does not mention when not to use it or suggest other tools for different key retrieval needs.

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