Get SAP Agent Profile

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. Description adds 'Free' and 'exact' and mentions it's a read-only SDK wrapper, reinforcing safety. No contradictions and adds marginal 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?

Three sentences: purpose, usage, broader context. Front-loaded with key functionality. Efficient without waste, though could be slightly tighter.

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 tool with one param, existing output schema, and rich annotations, description covers purpose, usage, and read-only context. Lacks details on edge cases (missing wallet) but adequate.

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 has 100% coverage and describes 'wallet' as Solana public key. Description only repeats 'by owner wallet' without adding extra semantics or format details. Baseline 3 maintained.

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 reads an SAP agent profile by owner wallet. Distinguishes from sibling tools like sap_profile_current (current user) and sap_profile_list (all). Explicit verb+resource+scope: 'Free exact SAP agent profile read by owner wallet'.

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?

Explicitly guides to use for a known agent before paid discovery or enrichment. Also mentions using reads to inspect chain state before mutations. Does not list exclusions or alternatives, but context is clear.

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