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

Without annotations, description discloses key behavior: transitions Draft and Rejected entries to Submitted, and billing-closed months are blocked. Could mention irreversibility or permissions, but adequate for a submission 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?

Three sentences, front-loaded with main action, no fluff. Efficiently conveys purpose, effect, and constraint.

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?

Covers key aspects: what is submitted, status transitions, blocking condition. No output schema, but the outcome is implied. Missing details on response or confirmation, but still fairly complete.

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%; description reinforces year/month and adds '1-12' range, but doesn't add new meaning beyond schema. Idempotency key description in schema already explains usage.

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 the action (submit), resource (time entries for a month), and effect (transition Draft and Rejected to Submitted). Distinguishes from sibling tools like approve_timesheet and reject_timesheet.

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?

Provides clear context: billing-closed months cannot be submitted, and specifies required inputs (year and month). Lacks explicit when-not-to-use or alternative tool names, but the condition is useful.

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