Give SAP Feedback

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

Annotations indicate a non-read-only, non-destructive operation; the description adds context about on-chain creation and the need for stability/auditability. However, it does not elaborate on side effects (e.g., irreversibility) or prerequisites beyond verification.

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 concise and the first sentence clearly states the primary purpose. The 'SAP MCP context' line is somewhat redundant given the title, but overall it is well-structured and not verbose.

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?

Given the presence of an output schema and full parameter descriptions, the description covers the basics. However, it lacks guidance on obtaining the target wallet PDA or when feedback is appropriate, leaving some context 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?

All four parameters are documented in the schema with descriptions (100% coverage), but the tool description adds no additional semantic detail beyond what is already in the schema parameters.

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 ('Create on-chain feedback') and the resource ('agent wallet'), and the 'SAP MCP context' line adds domain specificity. However, it does not explicitly distinguish this tool from siblings like `sap_update_feedback` or `sap_revoke_feedback`, relying on the name alone.

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 advises verifying the target agent PDA or wallet and ensuring data stability, which is helpful but provides no direct comparison to alternative feedback tools. No guidance on when to use this over update or revoke variants.

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