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

Beyond the annotations, the description discloses important behaviors: the submission is saved and asynchronous, a scoring job id is returned for later retrieval, requestId enables idempotent retries, and there is a one-free-score quota for signed-in students. This gives the agent a clear picture of side effects and constraints without contradicting the 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 four short sentences with no fluff. Each sentence contributes distinct value: the action, supported content, exclusions and return behavior, and idempotency/quota. Important information is front-loaded and the rest is 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?

For a complex tool with nine parameters and nested objects, the description covers the essential operational context: scope, exclusions, async behavior, job id retrieval, idempotency, and the free-score constraint. The output schema exists, so return-value details are not necessary, but a bit more guidance on optional modes like sample project versus the student's own project would make it fully complete.

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 low at 22%, so the description needs to compensate. It does summarize the major payload categories—text, subparts, drawings/photos, LEQ selection, CSP code, and Business project references—and explains requestId's retry role, but it leaves several parameters like intent, promptVariantId, and businessProjectPracticeMode to be inferred from the schema.

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 precise action: submits the student's own response to a Fiveable practice FRQ for saved, asynchronous scoring. It also distinguishes this tool from teacher assignments/exams and names the specific supported content types, making the tool's scope unmistakable.

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 clearly establishes when to use the tool: for student practice FRQs that should be saved and scored asynchronously. It adds the exclusion of teacher assignments and exams, though it does not explicitly name alternative sibling tools such as score_external_frq_response or check_practice_answer.

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