portal_assignments

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It introduces unsupported views ('today', 'recent') and omits the valid enum value 'all', so actual behavior is less predictable. It also does not mention default behavior, return format, pagination, or permissions.

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 appropriately short and front-loaded with the verb and resource. However, the inaccurate parenthetical enumeration adds noise and undermines the clarity that conciseness is meant to provide.

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 tool with no annotations and no output schema, the description should provide more behavioral context. The view options mismatch the enum, no default is clearly clarified, and return values/pagination are not mentioned, leaving an agent under-equipped to call it correctly.

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% and the single parameter is fully described by the enum, so the description does not need to repeat parameter information. Howver, the description's view list ('today', 'recent', 'archive') conflicts with the schema enum ('upcoming', 'archive', 'all'), potentially leading an agent to pass invalid values.

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?

Clearly states it retrieves homework assignments with a specific verb and resource, which distinguishes it from siblings like portal_exams and portal_evaluations. The parenthetical list of views is misleading because 'today' and 'recent' are not in the schema enum, but the core purpose remains 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?

The description implies appropriate usage by naming the resource, but it provides no explicit guidance on when to use this tool versus alternatives or which view to select. It mentions possible views, yet the view values contradict the schema, further weakening routing guidance.

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