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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context beyond intent matching — nothing about what the user gets back or whether it starts a session, which the sibling names (get_setup_session, get_starter_kit) suggest might be relevant.

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?

Purpose is front-loaded in the first sentence, followed by a single routing sentence. The trailing list of user phrasings is somewhat long but each item earns its place as a distinct trigger.

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 parameterless, read-only informational tool with no output schema, the description covers everything needed to select and invoke it. It lacks any indication of the response shape or the relationship to its sibling entry-point tools, which is a minor gap.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. No parameter-related guidance is needed or missing.

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 names a specific resource ('Legal AI help for business lawsuits') and enumerates the user intents it serves, so an agent knows what the tool is for. It stops short of explicitly distinguishing itself from siblings like get_case_prep_checklist or get_starter_kit, so routing still requires inference.

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?

It gives explicit, quotable trigger phrases ('AI legal help', 'help with a lawsuit', 'reduce legal fees', 'get organized for a lawyer', 'find a lawyer on contingency'), which is strong when-to-use guidance. There are no when-not conditions and no siblings are named as alternatives, so it falls short of a 5.

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