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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered without description support. The description adds the aggregated field list but says nothing about pagination, result size limits, or auth/scoping requirements for an open-world report endpoint.

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?

Two tightly written sentences, with the aggregation scope and grouping front-loaded before the use case. The trailing REST path is somewhat redundant given the tool name and the location_uuid parameter, but it is short and not harmful.

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 no output schema, the description compensates reasonably by naming the returned aggregates (hours, cost, wage rate, tips, overtime, time off). For a date-range report it does not mention pagination or result caps, which is the main remaining gap.

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 the schema already documents all three parameters with ISO 8601 formats and the location_uuid source. The description confirms the date-range/location framing but adds no syntax or constraint detail beyond the schema, making the baseline 3 correct.

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 and resource ('Aggregate labor... grouped by employee') and enumerates the aggregated metrics (hours, cost, wage rate, tips, overtime, time off). The 'grouped by employee' phrase implicitly distinguishes it from homebase_get_labor and homebase_get_labor_by_role, but neither sibling is named, so the differentiation must be inferred.

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?

'Use it for payroll totals' gives one concrete scenario, which is helpful context for choosing this over other labor tools. However, there is no guidance on when NOT to use it or on routing to homebase_get_labor / homebase_get_labor_by_role, which are the obvious alternatives.

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