edit_parent

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

With no annotations, the description carries full behavioral disclosure burden. It provides strong context: the permission requirement, partial-update semantics ('Only provided fields change'), and a safety-relevant effect ('existing student links are preserved'). This goes well beyond the raw 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 compact and well-structured: an opening purpose line, two behavioral notes, and a clean Args list. Every sentence adds useful information with no filler or repetition of schema details.

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 targeted guardian-edit tool, the description covers the required permission, how to obtain the required user_id, the partial-update behavior, and all parameters. An output schema exists, so not describing return values is acceptable. Nothing critical is missing for correct invocation.

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 0%, so the Args block is essential. The description explains all six parameters, clarifies which are optional, and adds critical usage guidance for user_id ('from list_parents') that the schema alone does not provide.

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 starts with a clear, specific verb and resource: 'Update a guardian's name, email, or phone.' This directly states what the tool does and distinguishes it from sibling tools like add_parent, invite_parent, or link_guardian_to_student.

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 gives useful context by noting the PS_ENABLE_WRITES requirement and instructing the agent to obtain user_id from list_parents(school_id). It does not explicitly state when not to use this tool in favor of an alternative, but the intended editing use case is clear.

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