Start Chore

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

With no annotations provided, the description carries the full responsibility for disclosing behavioral traits. It only states the action (start a timer, mark as in progress) without detailing side effects such as whether the timer automatically stops, what happens if the chore is already in progress, or whether it is reversible. No mention of permissions, rate limits, or return value format.

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 a single, concise sentence that gets straight to the point. It is front-loaded with the key verb and object, with no superfluous words. Every part adds value.

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?

The tool is simple with one parameter and an output schema, so the description need not explain return values. However, it lacks contextual details that would help an agent decide when to use it (e.g., state requirements, implications of starting a timer, interaction with pause/complete). A minimal but functional description, yet it could benefit from a brief note on typical usage or prerequisites.

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?

The input schema covers 100% of the parameters (chore_id with description). The tool description adds no additional meaning beyond reaffirming the parameter is the chore ID. Baseline of 3 is appropriate since the schema already documents the parameter and the description does not provide extra context.

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 the verb 'start' and resource 'chore timer', with clarification that it marks the chore as in progress. It is differentiated from siblings like pause_chore and complete_chore by focusing on the initial start action, making its purpose unambiguous.

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?

There is no guidance on when to use this tool versus alternatives. No mention of prerequisites (e.g., chore must exist or be in a specific state) or exclusions (e.g., not for paused or completed chores). Sibling tools like pause_chore and complete_chore exist, but the description does not clarify when start is appropriate.

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