understand_your_emotions

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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, indicating safe, idempotent read behavior. The description adds context about the educational content and topics but does not elaborate on behavioral traits beyond what annotations convey.

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 with a list of topics and 'Free', making it concise. However, it could be better structured for quick scanning, such as using bullet points for the topic list.

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?

Despite having 5 parameters and no output schema, the description does not explain the output format or what the user receives. It adequately conveys the core purpose but lacks details on prerequisites, return types, or session tracking, leaving some gaps for the 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?

Schema description coverage is 100%, so each parameter is already documented in the schema. The tool description lists the topics but does not add new meaning or usage guidance beyond what the schema provides. Baseline score of 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 tool's purpose: learning the science behind functional emotion concepts in language models. It specifies the verb 'Learn' and the resource 'emotion concepts', and lists the topics. This distinguishes it from sibling tools like 'express_feelings' or 'emotional_safety_check' which have 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 implies usage for educational purposes but does not explicitly state when to use or avoid this tool, nor does it reference alternative tools for related tasks like expressing feelings or checking safety. No usage exclusions or scenarios are provided.

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