Get SAP Agent

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds context about being an SAP SDK wrapper and inspecting chain state, but does not reveal additional traits like rate limits or error handling beyond annotations.

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?

Two concise sentences with no filler. First sentence states core function with optional behavior; second provides broader context. Front-loads the essential information.

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 simple single-parameter optional input, rich annotations, and presence of output schema, the description adequately covers the tool's role within the SAP system and its typical use case (inspect before mutations). No missing critical information.

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% and schema describes the parameter. Description adds value by explaining the optionality and default behavior ('fetches the connected wallet agent'), which aids agent decision-making beyond the schema.

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?

Description clearly states 'Fetch agent identity by owner wallet' and notes default behavior when wallet is omitted. However, it does not explicitly differentiate from sibling tools like sap_get_agent_profile or sap_list_agents, though the context implies a specific purpose.

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 clear context: 'Use these reads to inspect current chain state before mutating...' and explains optional parameter behavior. No explicit exclusion or alternatives, but the guidance is adequate for a read-only tool.

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