add_locked_date

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

With no annotations, the description explains the lock's effect, including the hierarchy of record types ('Higher-level locks supersede lower-level ones'). It does not cover authorization or side effects, but the behavioral context is adequate for an add 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 concise with a clear docstring format. Every sentence is informative, no unnecessary words. Parameter explanations are direct and well-organized.

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?

Given no output schema, the description covers all required inputs and the core behavior. It lacks information about response format, error handling, or authentication, but is sufficient for a simple creation tool.

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 compensates fully. It explains every parameter: from_date, to_date, reason, record_type (with enum meanings and hierarchy), and record_id. Adds significant meaning beyond schema titles/types.

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 states 'Add a locked date period,' which is a specific verb+resource description. It distinguishes from sibling tools like 'delete_locked_date' and 'list_locked_dates' by using 'add'.

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?

No guidance on when to use this tool versus alternatives. Does not mention prerequisites, context, or when not to use it. The description only defines the tool's function and parameters.

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