skylight_list_chores

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

Beyond the readOnlyHint=true annotation, the description discloses non-obvious return semantics: assignee is encoded in category_id, completed up-for-grabs chores carry completed_category_id, keys pluralize for multi-member links, and an absent singular key means unassigned. This is exactly the kind of behavioral context an agent needs.

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 tight sentences with the action and constraint front-loaded. The second sentence is dense but every clause adds essential detail about assignment-key semantics, and there is no filler.

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 list operation with no output schema, the description covers the trickiest return-value behavior and tells the agent how to resolve category names. It omits frameId semantics and pagination/ordering, but those are minor given the schema already documents the required date parameters.

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 schema already documents after/before with format and inclusivity, and the description only restates that they are a required date range. The optional frameId parameter has no schema description and the description does not clarify its role, so the description fails to compensate for that gap.

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 a specific verb and resource: 'List chores for a Skylight frame within a required date range.' This is clear and informative, but it does not explicitly differentiate from skylight_search_chores, so it stops short of fully distinguishing itself from siblings.

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?

It clearly implies usage when you need chores bounded by a required after/before date range ana gives a useful cross-tool pointer to skylight_list_categories for name resolution. However, it does not state when to prefer list_chores over search_chores or any exclusion criteria between the two.

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