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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantive behavior: explicit exclusions (raw meeting statements, private notes, unapproved suggestions, cancelled tasks) and the co-owner permission boundary, plus a reinforcement that it assigns or completes nothing. The permission semantics are genuinely beyond what annotations provide.

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?

Front-loaded with the resource, then exclusions and the permission caveat, then the read-only note. Every sentence carries weight, though 'This is read-only' mildly restates the annotation.

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 sketches the return (pending/completed state, prerequisites, attributed owner or relative due statement) and access restrictions. The one gap is the unexplained 'before' parameter, which leaves the filtering surface ambiguous.

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?

There is one parameter ('before') with 0% schema description coverage and no mention anywhere in the description. The description does not compensate for the gap, leaving the agent unable to know what 'before' filters or formats.

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 resource (your own household's explicitly approved meeting follow-up tasks) and enumerates scope: current pending/completed state, prerequisites, and owner/attribution. It clearly separates itself from the raw/private/unapproved/cancelled material it excludes, so an agent can tell what this returns without opening the schema.

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 supplies an access prerequisite (member-only tasks require the current owner; a co-owner Vault permission does not grant them) but never states when to use this rather than nearby siblings like get_meeting_prep, get_my_action_requests, or get_my_approved_artifacts. Usage is implied by the scope rather than routed.

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