Create time entry

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

Annotations indicate read-write, non-idempotent. Describes the total calculation formula, which adds value. However, lacks disclosure of side effects, required permissions, or return behavior (e.g., what object is returned on success).

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 concise sentences front-loading purpose and key formula. No wasted 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 8 parameters and no output schema, description covers core logic but does not explain return values, error conditions, or mention the activity_description_id parameter. Adequate but not comprehensive.

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?

Adds meaning beyond schema by explaining the relationship between quantity_in_hours and rate via total formula. Also clarifies billable vs non-billable. Schema coverage is 63%, and description compensates moderately.

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?

Clearly states 'Logs billable or non-billable time on a matter' which is a specific verb-resource combination. Distinguished from siblings like create_expense_entry, create_calendar_entry by focusing on time entry.

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 (e.g., create_expense_entry for expenses, create_calendar_entry for calendar events). Does not provide when-not or alternative tool references.

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