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

Beyond readOnlyHint=true, it discloses the key lifecycle fact that nothing is stored and the returned package must be kept by the agent, plus that multiple transcripts are parsed in parallel and that an ambiguous school aborts with candidates. These are real behavioral traits the agent cannot infer from the annotation or schema, though multi-call continuation is only covered in the schema description.

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 purpose is front-loaded in the first clause and the remaining sentences each carry distinct payload (downstream row shape, person prompts, parallel reading, ambiguity behavior, no persistence). Some sentences are awkwardly compressed ('A school several schools' names fit is answered with the candidates'), costing readability without adding length waste.

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 an output schema present, the description needn't explain return values, and it correctly focuses on ingestion behavior, ambiguity handling, and non-persistence for a nested 2-parameter tool. What remains thin is explicit sequencing relative to the many sibling tool names in the catalog.

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 coverage is 100%, so files/slot/school/unitid/content_base64/package are already documented, meeting the baseline of 3. The description reinforces the person-supplied nature of the school and the shape of downstream course/exam rows but adds no new syntax or constraint information about the parameters themselves.

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?

States a specific verb and resource: read a person's transcripts into their evidence package, producing file text/status plus course and exam rows. It also distinguishes itself from the downstream sibling by naming 'the items will_my_credits_transfer takes', so an agent can tell which tool ingests vs. which evaluates. The phrasing is convoluted in places but the core action is unambiguous.

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?

Gives procedural guidance ('Ask the person for each transcript and the school it came from') and explains the ambiguity path (several school matches returns candidates and reads nothing). It never states when to prefer this over siblings like get_persona_transcript or assemble_my_work_and_credentials, so the choice of tool is only implied by the 'evidence package' framing.

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