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

Without annotations, the description carries the full burden of behavioral disclosure. It reveals that entries are always attributed to the caller, returns per-item results with partial failures, and specifies constraints like max 50 entries and default start_time. It covers idempotency via the key parameter, though the key's details are in schema. Missing concurrency info but adequate for batch create.

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?

Three sentences, each earning its place: purpose, what to supply, and behavioral notes (attribution, partial failures, max). Front-loaded and no unnecessary words.

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 and no annotations, the description covers all key aspects: purpose, parameters, batch behavior, attribution, idempotency key reference, and constraints. Sufficient for an agent to understand and invoke the tool correctly.

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 100%, so baseline is 3. The description adds value by explaining defaults for 'start_time' (09:00), mentioning the max 50 entries, and describing partial failure behavior. This goes beyond just repeating schema descriptions.

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 'Create multiple time entries in one call', specifying the verb (create), resource (time entries), and batching aspect. It distinguishes from sibling 'create_time_report' (single entry) and 'bulk_update_time_reports' (update).

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 indicates when to use this tool: for creating multiple entries efficiently in one call. It provides context like maximum batch size (50 entries) and partial failure behavior. However, it does not explicitly contrast with alternatives like 'create_time_report' for single entries.

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