sap_fetch_feedback

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

No annotations are present, so the description must fully disclose behavioral traits. It only states 'Fetch' implying a read operation but does not mention side effects, permissions, authentication requirements, or what the output contains. The lack of detail on the feedback PDA structure or response format is a significant gap.

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 sentence, concise and to the point, including the essential parameters. However, it is very brief and could benefit from a more structured presentation with additional detail.

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 and no annotations, the description should provide more context about the return value, prerequisites, or interpretation of results. It does not explain what a 'feedback PDA' is, leaving the agent without sufficient information to fully understand the tool's purpose and output.

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%, so the baseline is 3. The tool description reiterates the schema's parameter info (agent PDA and optional reviewer wallet) but adds no new meaning beyond clarifying the optionality, which is already implicit from the schema not marking it as required.

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 the resource 'feedback PDA', with parameters specifying agent PDA and optional reviewer wallet. It distinguishes from sibling tools like sap_give_feedback by indicating a read operation, though the term 'feedback PDA' may be ambiguous without domain knowledge.

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 is provided on when to use this tool versus alternatives (e.g., sap_give_feedback, sap_update_feedback). The description lacks any context for suitable use cases or exclusions, leaving the agent to infer usage from the name alone.

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