create_time_entry

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

Annotations are minimal (readOnlyHint=false, destructiveHint=false). The description adds critical behavioral context: the tool requires a two-step confirmation (first call without confirm to see details, then set confirm=true). It also discloses that person_id can be 'me' if PRODUCTIVE_USER_ID is configured. This provides transparency beyond what annotations offer.

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 yet information-dense. It opens with the workflow step, then lists the workflow, followed by key requirements and behavioral notes. Every sentence serves a purpose, and the numbered list aids readability. Ideal length for quick parsing.

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 8 parameters (5 required), no output schema, and minimal annotations, the description covers all essential aspects: the complete workflow, prerequisites, confirmation mechanics, parameter details (including defaults for billable_time), and environment-specific behavior (PRODUCTIVE_USER_ID). An AI agent has sufficient information to 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?

While input schema covers all parameters (100% coverage), the description enriches meaning: for note, it advises specificity and bullet points (beyond schema's minLength); for confirm, it explains the two-step process; for person_id, it explains 'me' mapping. It also reiterates the workflow context for service_id and task_id. This adds value beyond the 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 'STEP 5 (FINAL) of timesheet workflow: Create a time entry with detailed work description.' It specifies the exact resource (time entry) and verb (create), and distinguishes from siblings like update_time_entry and delete_time_entry by placing it in a workflow context.

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 provides an explicit numbered workflow (list_projects → ... → create_time_entry) indicating prerequisites. It details required fields (service_id, note min 10 chars) and optional task_id. It explains the confirmation process with the confirm parameter and the 'me' shorthand for person_id based on environment configuration. This guides when and how to use the tool versus alternatives.

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