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

Beyond the annotations (readOnlyHint=false, destructiveHint=true), the description discloses crucial behaviors: it requires user consent before sending data externally, must not be called without consent, and must not fabricate user feedback. This adds significant transparency about side effects and ethical constraints.

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 somewhat repetitive, re-emphasizing the consent requirement and the prohibition on inventing feedback in multiple phrasings. It could be more concise, but the structure is clear and the key points are all present.

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 description provides all necessary context for correct and ethical use: consent procedure, verbatim quoting, and the prohibition on fabricating feedback. It fully addresses the tool's purpose and constraints, making it self-contained for an agent.

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?

While the schema covers all parameters, the description enriches semantics by explaining that 'consented' must only be true after explicitly asking, 'in_their_words' must be verbatim, and that 'verdict' reflects the user's reaction. It also clarifies optional fields like 'expected' and 'track_id' with contextual meaning.

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 title and description clearly state the tool's function: sending user feedback to AINSOF, with explicit emphasis on obtaining consent. It is distinct from sibling tools like search_music or analyze_video, which serve different purposes.

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 provides explicit usage instructions: ask the user for consent every time, only send if they agree, never invent feedback, and quote the user verbatim. It also implies when to use this tool (when the user provides feedback on another tool's output) and contrasts with siblings by focusing on the feedback-sending role.

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