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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description reveals that the tool creates a 7-day task as part of deferring the recommendation. This adds meaningful behavioral context, though it does not specify what happens to the original recommendation (e.g., whether it remains pending).

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, compact sentence that front-loads the 'Add Later' label and communicates the action and its consequence without any wasted words. It is highly efficient and easy to scan.

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?

For a simple tool with one parameter and an output schema, the description provides sufficient context about the action and resulting task. It does not need to explain return values since an output schema exists. A minor gap is the lack of clarification about the recommendation's state after deferral, but this is not critical.

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 already provides 100% parameter coverage, including an example and a clear description of recommendationId as the id from get_house_review. The tool description adds no additional parameter semantics, so the baseline score of 3 is appropriate.

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 opens with 'Add Later' and clearly states 'defer a House Review recommendation and create a 7-day task'. The verb 'defer' and resource 'House Review recommendation' are specific and distinguish this from sibling tools like skip_recommendation and create_task.

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 implies usage context through 'Add Later' but does not explicitly state when to use this tool versus alternatives, nor does it exclude scenarios like permanently skipping a recommendation. A clear comparison to skip_recommendation would strengthen this dimension.

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