bb_assignment_details

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

The annotations declare readOnlyHint=false, which looks odd for a 'read' tool, but the description explains exactly why: the tool writes attachment files to local disk when download=true. That is genuine behavioral context beyond the annotations. It still does not describe pagination or how much of an assignment body is returned, though the output schema covers return shape.

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 tight clauses with the payload described first and the side effect second, so nothing is wasted. The telegraphic 'keyword 为 ID/唯一名称' phrasing is efficient but slightly clipped.

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?

An output schema exists and annotations are present, so return values and safety profile need not be restated. The remaining gap is the undocumented required course parameter and the lack of any routing cue relative to the list and download siblings, which matters for a detail-fetch tool in an eight-tool family.

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 0%, so the description must carry parameter meaning. It explains keyword as an ID or unique name and spells out the download=true condition, but the sole required parameter, course, is not explained at all. Two of three parameters are clarified, so it partly fills the gap rather than fully compensating.

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 uses a specific verb (读取/read) and resource (作业/assignment), and enumerates what the agent will see: full requirements, status, grade and attachment list. This clearly distinguishes it from action siblings like bb_submit_assignment, though it never explicitly contrasts itself with bb_list_assignments or bb_download_courseware.

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?

It implies the usage context (fetch full detail for one assignment, identified by keyword), and gives the conditional rule for attachment downloading. However, it gives no guidance on when to pick this over bb_list_assignments for an overview, and no prerequisites such as needing a course identifier first.

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