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

Annotations already declare that this is a non-read-only, idempotent, non-destructive, closed-world mutation. The description adds useful behavioral context beyond that: it says contacts are masked, states that the response includes missing[] and ready_to_finish, and clarifies that projects are created rather than updated. It does not contradict the annotations.

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 two tight sentences with no wasted words. It front-loads the main action and scope, then adds return behavior and the masking note.

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 an 11-parameter mutation tool with nested objects and no output schema, the description covers the main purpose, form areas, return indicators, and masking behavior. It is still somewhat incomplete on when to use this versus save_project or interview tools, but the schema handles parameter-level detail thoroughly.

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%, so all 11 parameters are already documented in the schema. The description adds a useful grouping of the form contents (profile fields and up to 5 projects) but does not provide syntax or behavioral detail beyond what the schema already states for parameters such as dry_run, wait_s, submit_to_interview, and request_key.

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 states a clear verb and resource: filling in the Tavern form about a person, including profile fields and up to 5 projects. It is specific enough to distinguish this from generic messaging or interview tools, but it does not explicitly differentiate itself from the close sibling save_project, which handles project updates.

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 says what the tool does but gives no explicit guidance on when to use it versus alternatives such as save_project, interview_start, or interview_answer. The only routing hint (projects create NEW projects; update via save_project) is in the parameter schema, not the description, so an agent reading only the description has no usage boundaries.

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