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

With annotations only providing readOnlyHint, the description adds rich behavioral context: the three-state output semantics (covered/missing/unknown), the guarantee that 'unknown' is never a guess, the caveat that this is 'a case to argue, not a verdict,' and detailed source attribution rules. It also explains version and source counts for multi-form records and the behavior for records last seen in older editions. This goes well beyond what the annotation conveys.

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 front-loaded with the core question, but it then becomes a long, dense block that explains output states and source attribution in detail. Because an output schema exists, much of the return-value explanation is redundant and could be trimmed. The text is not wasteful enough to score 1 or 2, but it is far from concise.

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 domain complexity and the presence of an output schema and readOnly annotation, the description supplies all the context an agent needs: what is evaluated, what the states mean, how sources are attributed, and the important caveat that recognition is the school's act. It covers edge cases like multi-form records and older editions that a caller would otherwise have to discover. The definition is complete for correct invocation.

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?

Schema description coverage is 100%, so the input schema already documents the held array, checklist_id, and target_unitid thoroughly. The description reinforces the kinds of held items (AP, CLEP, IB exams, courses) and the target school, but adds little syntax or format meaning beyond the schema. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 states a specific question and resource: whether prior credits (AP/CLEP/IB exams or courses) apply as credit at a target school. It is highly specific about the evaluation's three states and output fields. It does not explicitly differentiate itself from sibling tools, but the purpose is clear enough to distinguish it from general lookup tools.

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 usage by explaining what the tool answers and when each state occurs, but it never states when to use this tool versus alternatives such as find_agreements or compare_destinations. There is a note that forms come from the one-record get, never from a list, which is a retrieval instruction but not an explicit usage guideline. Guidance is implied rather than stated.

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