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

With no annotations, the description carries the burden and does disclose the required permission level and the conditional irrelevance of anchor_date. It does not say whether setting a period overwrites prior configuration, affects already-recorded hours, or is reversible — meaningful gaps for a mutation tool.

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 sentences, front-loaded with the actor and action, then the one non-obvious parameter rule. The parenthetical carries dense, necessary conditional logic 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?

Output schema exists, so return values need not be explained. However, for an unannotated config mutation, the description omits what happens to existing periods/hours and whether re-invocation overwrites — material context the schema cannot supply.

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 0%, so the description must compensate. It explains anchor_date thoroughly (first day of a period; ignored for semimonthly/monthly) and defines the semimonthly boundaries, but says nothing about shop_id beyond its existence, leaving one of three parameters undocumented.

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 ("set the pay period"), which is distinguishable from payroll_getPeriod and payroll_hours. It doesn't explicitly name those siblings, so the differentiation is inferable rather than stated.

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?

"Owner or office" gives the calling role, which is a real usage constraint, but there is no statement of when to call this versus payroll_getPeriod or before/after running payroll_hours. Usage is implied rather than guided.

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