sap_sns_get_record_pda

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

The description only says 'Derive' implying a pure computation with no side effects. There are no annotations to indicate safety. It adds minimal transparency beyond the basic verb.

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?

One sentence, 14 words, no filler. However, it could be slightly expanded to include return value type for completeness 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 output schema, the description should clarify what the tool returns (e.g., a base58 address). It lacks context on PDA derivation purpose and how the result is used. Incomplete for a derivation tool.

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%, so baseline 3. The description restates the parameter concepts without adding new details. It does not explain parameter constraints, formats, or examples 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?

The description clearly states it derives the SNS record PDA, specifying the inputs (domain and record type). It distinguishes from siblings like sap_sns_get_record (which fetches) and sap_sns_get_domain_pda (which gets domain PDA). However, it doesn't explicitly mention the output format.

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 guidance on when to use this tool versus alternatives. The description does not mention prerequisites, when not to use, or how it compares to sibling functions like sap_sns_get_record or sap_sns_check_domain.

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