bulk_invite_parents

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

The description discloses that the tool requires PS_ENABLE_WRITES (a prerequisite) and that it automatically skips already registered guardians, which is a behavioral nuance not apparent from the schema or annotations. It also indicates that the response reports how many were notified, which adds transparency about output. This is valuable beyond the schema.

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 well-structured, with a clear purpose statement, behavioral notes, and a concise parameter section. It is front-loaded with the most important context (what it does and the requirement), followed by workflow details. No superfluous wording.

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 tool's moderate complexity (two params, clear purpose) and the presence of an output schema (not provided in detail but indicated), the description covers the essential aspects: purpose, prerequisites, parameter semantics, and behavior. It does not explain the output format in detail, but the output schema is available, and the description mentions the response reports notified count. This is complete enough for an agent to use 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?

The schema provides only names and types (school_id: integer, user_ids: array of integers), with 0% schema description coverage. The description adds critical meaning by explaining that user_ids come from list_parents and should be unregistered guardians. It also implicitly defines school_id as the identifier for the school. This compensates for the lack of schema descriptions, though it could be more explicit about the exact format or constraints.

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 action (send registration invitations), the target (multiple guardians), and the purpose (to register them). It distinguishes itself from the sibling tool 'invite_parent' by focusing on bulk invites, and it refers to related tools like 'list_parents' for context.

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 explicitly states when to use this tool ('to invite all' unregistered guardians) and provides a clear workflow: get user_ids from list_parents(school_id), typically those with registered=false. It does not explicitly mention when not to use it, but the workflow is specific enough to guide the agent.

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