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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed world), so the description rightly focuses on content scope and semantics. It adds genuinely useful context beyond annotations: that marks are user-authored life context to factor into interpretation, and that reading should precede editing. No mention of auth, limits, or paging, but those are minor for a zero-param read.

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?

Three compact sentences, front-loaded with the verb and resource list, and each subsequent sentence adds a distinct piece of guidance (interpretation, sequencing). No filler, though the resource enumeration partially overlaps with the title's framing of 'telo home'.

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 zero parameters, an output schema, and full annotation coverage, the definition supplies what the structured fields cannot: the meaning of marks and the read-before-edit rule. Only the scope of 'recent changes' is left unspecified, a small gap for a read tool.

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?

Zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description adds no parameter guidance but none is needed.

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?

States a specific verb ('Read') and names the concrete resources returned: cards on the home screen, dated marks, and recent changes. This clearly separates it from mutating siblings like edit_card or arrange_home, though the domain jargon ('telo home', 'cards') is only inferable from the title and 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?

'Call before editing the home' gives explicit sequencing guidance relative to the editing siblings, and 'use them when interpreting their data' tells the agent what to do with marks. It stops short of naming the specific alternative tools (arrange_home, edit_card) or stating when not to call it.

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