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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that it returns background/pricing info, which is consistent. It does not detail the output format or any access constraints, but the bar is lower given annotations.

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 that packs in the purpose, scope, timing, and where to find related resources. It is front-loaded with the key action and resource, followed by useful details. No wasted words.

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?

Given the tool has no parameters, no output schema, and simple annotations, the description is complete. It tells the agent exactly what the tool provides and the context for its use. There are no missing details that an agent needs to invoke it correctly.

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?

Since the tool has zero parameters, the description does not need to explain parameter semantics. The schema coverage is 100% (vacuously), so a baseline of 4 is appropriate because the description provides context about what the information covers.

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 provides background and pricing for a specific migration map, including unsupported features, timing, and where to find the free map and paid monitoring. It is distinguished from siblings by focusing on background/pricing rather than listing breaking changes or endpoint lookups.

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 use for planning a HubSpot API migration, which is helpful context, but it does not explicitly say when not to use it or name alternatives. However, the sibling list and the specific focus on background/pricing provide implicit guidance.

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