skylight_search_chores

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

No annotations are provided, so the description carries the full burden. It only mentions the inclusion of unscheduled/template chores, but does not disclose whether the tool is read-only, any authentication needs, rate limits, or other behavioral traits. This leaves significant gaps for an AI agent.

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 sentence that front-loads the key differentiator (including unscheduled/template chores). It is concise and avoids unnecessary words, though it could benefit from slight restructuring for clarity.

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?

With 5 parameters, no output schema, and no annotations, the description is too brief. It does not explain return format, pagination via limit, filtering by frameId, or the role of include_up_for_grabs. The tool requires richer context for correct invocation.

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 40% (only search_query and ended_chore_lookback_days have descriptions). The description adds no additional meaning beyond the schema; it does not explain the purpose of any parameters (e.g., limit, frameId, include_up_for_grabs), failing to compensate for the low coverage.

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 identifies the tool as a search for chores, specifically including unscheduled/template chores that the date-range list cannot return. This differentiates it from sibling tool skylight_list_chores, providing a specific verb and resource.

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 when needing unscheduled/template chores not available via the date-range list, providing some context. However, it does not explicitly state when to avoid this tool or mention alternatives like skylight_list_chores.

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