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

Annotations only indicate generic read-only/destructive hints, so the description adds meaningful behavioral context by disclosing that this operation creates an assignment and rejects allocations over 100% capacity unless allow_overbooking is true. It does not describe error responses or effects on existing assignments, but the core validation behavior is usefully surfaced.

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 front-loaded: it states the action first, then the key allocation_type constraint, then the capacity rule. There is no filler, repetition of the title, or unnecessary detail.

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?

The description captures the essential action and the most important validation rule, making a basic call plausible. But with 8 parameters, low schema coverage, and no output schema, it leaves missing details such as return behavior, end_date semantics, and the relationship between allocation_type and its numeric fields. It is adequate but not fully complete for an agent invoking edge cases.

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 only 38%, so the description must compensate for undocumented parameters. It partially does by naming allocation_type values and explaining the allow_overbooking bypass. However, it leaves gaps around how allocation_hours and allocation_percentage map to the two allocation types and what end_date/period means for the capacity check.

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 opens with a specific verb and resource, 'Assign an employee to a project,' which clearly expresses a team-member add operation. It is distinct from sibling tools like projects_update_team_member, projects_remove_team_member, and projects_add_document. The allocation_type mention reinforces that this is about staffing, not documents, pricing groups, or other project resources.

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 implies the primary use case: assign a new employee to a project. However, it does not explicitly state when to use this tool over alternatives such as projects_update_team_member, projects_remove_team_member, or resources_create_allocation. The agent must infer the correct tool primarily from the name and title.

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