get_course_people

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

With no annotations, the description must disclose behavioral traits itself. It only says 'List' (implying read-only) but does not state it explicitly, nor mention pagination, response format, or any side effects. Additionally, the account parameter is undocumented in the description, creating a hidden behavioral aspect.

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 has a concise one-sentence summary followed by a structured argument list. It avoids redundancy and is well-organized, though the argument list could be slightly more compact.

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 3-parameter tool with no annotations, the description is incomplete. It omits the account parameter, does not explicitly confirm the read-only nature, and provides no details on return structure (though an output schema exists). The lack of behavioral disclosure makes it insufficient for an agent to call it without guesswork.

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?

The schema has no parameter descriptions (0% coverage), so the description must compensate. It explains course_id (source from get_courses) and role (allowed enums and default behavior), which adds meaning. However, the account parameter is entirely omitted, leaving a third of the parameters unexplained.

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 'List people enrolled in a course, optionally filtered by role' – a specific verb and resource. It is distinct from siblings like get_assignments or get_announcements, which handle different entities, so an agent can immediately understand what this tool does.

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 usage context by instructing to obtain course_id from get_courses and explaining role filtering with allowed values. It does not explicitly exclude alternatives, but the tool's purpose is narrow enough that siblings are clearly different. No misleading guidance.

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