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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does add meaningful context by listing per-endpoint pricing (e.g., 'match ($0.10)', 'crisis (FREE)') and noting that crisis routing is 'ALWAYS FREE'. However, it does not describe response format, error behavior, authentication requirements, or whether the tool is read-only. The cost and the crisis-free emphasis are useful, but broader behavioral traits are absent.

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 front-loaded with the core purpose ('MindPulse: Global mental health intelligence API') followed by a structured bullet list of endpoints. Each line is informative and distinct, listing the action name, price, and a brief description. It is somewhat lengthy (12 bullets), but every line carries useful information without redundancy. The structure is easy to scan.

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 tool has 23 parameters and no output schema or annotations, so the description carries substantial responsibility. It covers the 12 actions well and mentions global coverage, but does not explain how the remaining 22 parameters relate to specific endpoints, what responses look like, or any usage flows. It is adequate for understanding the tool's scope but incomplete for full operational clarity, especially given the complexity.

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%, providing all parameter descriptions, so the baseline is 3. The description adds value by expanding the 'action' enum with endpoint-specific meanings (e.g., 'burnout: Burnout assessment and recovery protocol', 'addiction: Addiction support and harm-reduction guidance'), which helps an agent select the correct action. It also includes per-action pricing that informs decision-making. Other parameters are not expanded, but the schema already covers them.

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 opens with 'Global mental health intelligence API' and lists 12 specific endpoints (match, assessment, burnout, etc.) with one-line explanations (e.g., 'Therapy platform matching', 'Burnout assessment and recovery protocol'). This clearly identifies the tool's domain and sub-capabilities, and distinguishes it from sibling *pulse tools by focusing on mental health intelligence.

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?

While there are no explicit 'when to use' or 'when not to use' statements, the endpoint list provides clear context for each action (e.g., 'sleep: Sleep disorder guidance (CBT-I protocol)'). The tool's self-identification as a mental health intelligence API makes the use-case obvious. It lacks explicit exclusions or alternatives, but the domain specificity and endpoint mapping offer sufficient guidance.

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