Get teacher feedback for a student

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered, yet the description adds valuable non-obvious context: the return content is third-party authored and untrusted, with an explicit instruction to treat it as data rather than instructions. It also discloses the shape of returned items. It does not mention pagination or rate limits.

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, both earning their place: the first defines scope and payload, the second delivers the security-relevant instruction. Front-loaded and free of filler.

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 steps in by enumerating the fields each feedback item carries, and the prompt-injection warning covers the main risk of returning untrusted content from an open-world source. Only pagination/volume behavior is left unaddressed, which is minor for this read tool.

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 a single parameter, so the schema already documents artist_id fully including its pattern. The description only reinforces the source of the ID (list_students) and adds no format or constraint detail beyond the schema. Baseline 3 applies.

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?

States a specific verb (list) and resource (teacher feedback on a student's artwork), then enumerates the returned fields (message, poster, timestamp, artwork, read status). Distinguishable from close siblings like artsonia_list_comments and artsonia_mark_feedback_read without opening any schema.

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?

Tells the agent where the artist_id comes from (artsonia_list_students), which is actionable context, but gives no when-to-use vs. when-not guidance against siblings such as list_comments or mark_feedback_read. Usage is only implied by the resource named.

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