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

Annotations already declare readOnlyHint, non-destructive, and non-open-world, so the safety profile is covered. The description adds meaningful context beyond them: it reads the stored page rather than triggering a build, and it explains that returned items carry ids usable in other tools.

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 tight sentences, front-loaded with the resource definition before the follow-up routing. Every sentence carries distinct information: content, id handoff, prompt execution, and the no-build constraint.

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 no output schema, the description usefully characterizes what comes back (sections of suggestions, attention items, drafts, staged work, each with an id) and how to act on it. Nothing needed to call it correctly appears to be missing.

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 description coverage is 100% and the enum of 14 sections is fully documented in the schema, so the schema carries the burden. The description adds no syntax or formatting guidance for limit or section, which matches the baseline 3 for high-coverage schemas.

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 and resource ('What is on the person's Home page') and enumerates the content classes (suggestions, attention items, drafts, staged work), which distinguishes it from the sibling list/get tools. It also explicitly names the follow-up tools update_home_item and ask_zenning.

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?

Gives explicit routing: item ids go to update_home_item for done/dismiss/snooze/restore, and suggested prompts go to ask_zenning. It also states a negative condition ('does not start a build'), so the agent knows what this call will not do.

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