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

Annotations already mark readOnlyHint=true and destructiveHint=false; the description reinforces this by explicitly noting it is the intake path and that the applicant confirms via SetClasses at a later step. It discloses the read-only, advisory nature of the operation beyond the annotation. It does not cover edge cases such as existing class selections or error conditions, but adds meaningful context beyond what annotations provide.

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?

Three sentences, front-loaded with the core behavior and outcome. The example about 'accounting classes' is illustrative and precise, and the explicit note that it writes nothing is useful and compact.

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?

Covers what it does, why it exists, and the follow-up action for the agent to take. It does not describe output/return format, but the presence of an output schema reduces the burden on the description to explain results.

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 has 100% coverage of parameters and the only parameter (applicationId with a UUID string wrapper) is self-explanatory. The description adds nothing about the parameter. Since the schema fully documents itachine, a 3 is appropriate per the baseline rule.

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 a specific verb and resource:

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?

Explicitly positions itself as the intake path and contrasts with SetClasses, where the applicant confirms. It also gives an example of the problem it solves (accounting services vs software), making the when-to-use scenario concrete. This clearly directs the agent to use this tool before claiming classes and to use SetClasses afterward.

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