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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context that no annotation supplies: the payload contains section prompts, per-section answer formats, and answers collected so far, and that some visual sections can only be completed in the web app, implying partial/read-only answer data. It stops short of describing completeness or missing-section behavior more precisely.

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?

Two sentences, front-loaded with the resource and the three things returned, with no filler. The trailing web-app caveat is short and earns its place because it warns about data that cannot be set through this interface.

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 sketch the return shape, and it does so at an appropriate level for a read-only two-parameter tool whose schema is fully documented. It could say a bit more about what identifies the assignment (status, mentee, due state), but nothing essential for calling it correctly is missing.

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%, with 'program' documented as an id or domain and 'assignment_id' constrained to a 24-hex pattern, so the schema carries the parameter burden. The description adds no additional meaning about the relationship between the two parameters or what happens if the assignment does not belong to the given programme.

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 a specific resource ('One assigned mentoring tool') and enumerates what it returns: section prompts, the answer format per section, and existing answers. That is enough to distinguish it from list_mentoring_tools or list_tool_catalog, though the retrieval verb itself is only implied by the tool name rather than stated.

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 is only implied: fetch a single assignment to read its sections and answers. There is no explicit statement of when to pick this over list_mentoring_tools or get_form, and no prerequisites or error conditions (e.g. invalid or foreign assignment_id) are mentioned. The web-app caveat is a limitation note, not alternatives guidance.

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