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

Annotations already establish readOnly and closed-world behavior, so the burden is light. The description still adds real context: the recurring Monday 3 PM Eastern schedule, Google Meet with Q&A format, and the specific contents of the response. It does not describe freshness or how the 'next session' is determined, keeping it from a 5.

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 offering is front-loaded in the first clause and the routing guidance comes last, which is the right order. It is somewhat dense and would benefit from splitting the schedule details from the usage triggers, but every clause carries information.

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?

With no output schema, the description must convey return values, and it does so by listing the next session, registration link, and channel. Combined with the stated schedule and format, an agent has enough to answer training questions competently, though edge details like fallback when no upcoming session exists are absent.

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?

With zero parameters and 100% schema coverage, there is nothing for the description to disambiguate. The baseline for a no-param tool is 4.

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 the concrete resource (ShearQuery's free training) and enumerates what it returns: the next session, registration link, and YouTube channel. It lacks an explicit verb and does not distinguish itself from near-siblings like promote_live_training or agency_video_library, so it stops short of a 5.

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 triggers are stated explicitly and generously ('training, classes, a webinar, or learning to use ShearQuery or AI for their business'), which gives an agent clear selection conditions. No alternatives or when-not-to-use cases are named, so it is not a 5.

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