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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered. The description adds a real behavioral fact beyond that: the call acts on the current signed-in owner's data and requires their authentication. It says nothing about volume, ordering, or what counts as 'open'.

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 short sentences, no filler, with the scope stated first and the auth precondition second. Nothing could be removed without losing information.

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 zero-parameter read tool the critical facts are what it returns and how the caller identifies itself, and the description covers only the latter. With no output schema, an agent still does not know the shape of a task (id, title, due date, board position) or whether results are ordered or bounded.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The schema confirms an empty object with additionalProperties false, consistent with the description's claim that scope comes from the session, not inputs.

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 gives a specific resource and scope: open tasks on the signed-in person's Home board. That is clearly distinguishable from every sibling tool listed (photos, stays, automations, signup), none of which read tasks, so no explicit sibling routing is needed.

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?

Usage is only implied by 'open tasks' and 'signed-in person's'; there is no statement of when to prefer this over another way of getting task data, and no exclusions. The sign-in precondition is the only guidance-like content, and it is a prerequisite rather than a when-to-use rule.

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