sap_get_agent_profile

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

No annotations are provided. The description says 'Fetch', implying a read-only operation, but does not disclose side effects, authentication requirements, rate limits, or what 'hydrated' entails. The behavior is underspecified.

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, efficient sentence with no wasted words. However, it could be slightly more informative without losing conciseness.

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 no annotations, no output schema, and a parameter that appears optional in schema but required in practice (wallet), the description lacks context on what a 'hydrated' profile includes, error conditions, and complete parameter semantics. It is insufficient for agent to invoke correctly without additional knowledge.

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 description coverage is 100% for the single parameter 'wallet', explaining it is a Solana public key in base58. The description adds 'hydrated' and 'by owner wallet', which align with the schema but do not significantly enhance meaning beyond what schema already provides.

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 verb 'Fetch' and resource 'hydrated SAP agent profile' with method 'by owner wallet'. Among sibling tools like sap_get_agent and sap_get_agent_stats, this tool specifically targets profiles, making it distinct.

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?

No explicit guidance on when to use this tool versus alternatives such as sap_get_agent or sap_get_agent_stats. The description implies usage for fetching a profile by wallet but does not mention exclusion criteria or when to prefer other tools.

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