get_gradebook_history_feed

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

Annotations declare readOnlyHint=true, indicating a safe read operation. The description adds behavioral details: the feed is paginated, optionally filterable by assignment/user, and sortable oldest-first. These details go beyond the annotation's declarative hint, providing actionable context for the agent.

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 a single concise sentence that efficiently covers the tool's core functionality, optional filters, and sorting capability. Every word earns its place, and no redundant or unnecessary information is present.

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?

Given the parameters and annotations, the description covers the key features (pagination, filtering, sorting) but lacks details about the return format or what constitutes a feed entry. Since there is no output schema, the agent might benefit from more context on the response structure.

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?

With 100% schema description coverage, the schema already documents each parameter. The description reinforces the purpose of assignment_id, user_id, and ascending by restating the filtering and sorting options, but does not add new semantic meaning beyond what the schema provides.

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 clearly states the tool retrieves a paginated gradebook history feed for a course, with optional filtering and sorting. It is specific and actionable, but does not explicitly contrast with sibling tools like list_gradebook_history_days or list_gradebook_history_submissions, which might also be used for gradebook history.

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 provides context for when to use the tool (get a paginated feed, optionally filtered/sorted), but does not give guidance on when not to use it or how it compares to alternatives. For example, it does not explain when to use this over list_gradebook_history_submissions.

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