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

Beyond the annotations, the description discloses a key behavioral rule: the allocation is rejected if total capacity in the window would exceed 100%, unless allow_overbooking is true. It also clarifies that this allocation type is not project-scoped, which is useful behavioral context. It does not cover side effects or persistence details, but the annotations already signal a non-read-only, non-destructive operation.

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: it front-loads the core distinction, names the alternative, and then states the required field and overbooking constraint. Every sentence contributes useful information, with no filler or repetition beyond what is already in the schema.

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?

With 8 parameters, no output schema, and low schema description coverage, the description is not complete enough for an agent to invoke the tool confidently. It gives the essential orientation but omits important details like how to specify hours versus capacity, what date format is expected, and what the response will look like.

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%, and the description does not sufficiently compensate. It mentions activity_type_id as required and references the capacity check, but it does not clarify the meaning of allocated_hours versus allocated_capacity, how employee_id should be provided, date formats, or the note field. Agents are left guessing on several important parameters.

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 identifies a manual allocation tied to an activity type, not a project, and explicitly names the sibling tool for project allocations. The verb, resource, and scope are specific enough to distinguish this tool from projects_add_team_member and other siblings.

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 states when to use this tool: for manual allocations tied to activity types, not projects. It explicitly says to use projects_add_team_member for project allocations, giving the agent a clear routing decision and an exclusion condition.

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