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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds behavioral context beyond annotations: it is an informational starting point, it routes non-qualifying users elsewhere, and it defines a follow-up action. It does not detail return format or pagination, but that is a minor gap for a simple read-only tool.

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 compact and well-structured: it front-loads the primary usage ('START HERE'), then states what is returned, who is excluded, and what to do next. Every sentence provides distinct value with no filler or redundant restating of the tool name or title.

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?

For a one-parameter, read-only informational tool, the description is complete. It covers the target audience, the content returned, the exclusion case, and the follow-up tool. No output schema exists, but the description sufficiently explains what the agent can expect to deliver to the visitor.

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?

The schema already provides a thorough description of the only parameter, context, including word-count requirements, perspective rules, and sensitive-data restrictions. The tool description does not add parameter-level detail, but with 100% schema description coverage, the baseline 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 opens with 'START HERE' and states exactly what the tool returns: how company membership works, community reach figures, and the two qualifying questions with valid answers. It clearly targets companies considering an ELC membership and distinguishes itself by routing individual mentor-seekers to /mentor/ and pointing to match_package as the next step, so it does not blur with siblings.

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?

Usage guidance is explicit: 'START HERE for any company considering an ELC membership' with personas listed. It also states when not to use it ('Companies only — individuals seeking a mentor for themselves get pointed to /mentor/ instead') and names the follow-up tool ('After the visitor answers both questions, call match_package'). This gives clear decision rules and routing.

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