Get SAP Agent Profile

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the term 'hydrated' and 'SDK wrapper' but does not provide additional behavioral context such as rate limits, authorization requirements, or what 'hydrated' entails beyond the output schema. Minimal value added.

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 two sentences: first delivers the purpose, second provides context and usage. No redundant words; efficient and front-loaded.

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?

The tool has one parameter, no enums, and an output schema. The description explains when to use (before mutations) but is generic. It is complete enough for a simple read tool, though a note on the 'hydrated' content would be helpful.

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?

Input schema has 100% description coverage, and the description merely says 'by owner wallet', which echoes the schema. No significant extra meaning is added. Baseline 3 is appropriate.

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: 'Fetch a hydrated SAP agent profile by owner wallet'. It provides a specific verb and resource. However, it does not explicitly differentiate from the sibling tool 'sap_get_agent', which might serve a similar purpose by a different key.

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 includes a general usage guideline: 'Use these reads to inspect current chain state before mutating...' but this is generic advice for all SAP read tools, not specific to this profile tool. It does not compare against alternatives like 'sap_get_agent' or 'sap_get_agent_stats'.

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