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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The 'WRITE:' prefix and endpoint add mild context, but the description does not elaborate on the destructive implication, auth requirements, or side effects of creating this parent profile.

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?

Three tight clauses with the operation type ('WRITE:') front-loaded followed by the domain definition and the sibling follow-up. Every sentence earns its place with no 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?

For a 12-parameter write tool with no output schema and merely 33% schema coverage, the description explains the entity and workflow adequately but leaves most parameter semantics undocumented. The safety profile is carried by annotations, but parameter guidance is thin for a tool of this size.

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 coverage is only 33% (4 of 12 parameters documented), which is below the 50% threshold, so the description must compensate but does not. It offers no parameter guidance, omitting even the required first_name/last_name and the status enum's 'Prospective' lead semantics.

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+resource ('create a family customer') and defines the novel domain entity as 'the billed parent profile that child students belong to'. It distinguishes itself from sibling teachworks_create_child_student by naming it and clarifying the ordering relationship.

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?

Gives clear workflow context: add children afterwards with teachworks_create_child_student, and the endpoint POST /customers/family. It stops short of explicit when-not conditions or prerequisites (e.g. required permissions), so it is slightly below the top tier.

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