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

No annotations are provided, so the description carries the full burden. It does disclose the composition of returned data (calendar, reminders, note titles, conversation starters), which is genuinely useful behavioral context, but it says nothing about permission requirements, freshness/recency windows (how recent is 'recent'?), or whether the call has any side effects.

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?

A single front-loaded sentence-fragment that enumerates outputs in priority order with zero filler. Every clause earns its place.

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 and no annotations, the description must convey what comes back, and it does so by listing the four content sections. It's adequate for a zero-required-parameter read tool, though the absence of any indication of return shape or data freshness leaves a small gap.

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 coverage is 100% with a single optional enum parameter ('operation': 'today') fully documented in the schema. The description adds nothing about the parameter, but the schema already does the work, so baseline 3 applies.

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 names a concrete composited output: today's calendar, due reminders, recent note titles, and conversation starters. It's clear what the tool produces, and the enumerated sections implicitly map to the calendar/notes/reminders siblings, but it never explicitly states that this is a composite that replaces calling those siblings separately.

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?

'One-shot day briefing' hints that this is the single-call alternative to hitting calendar, reminders, and notes individually, but no explicit when-to-use or when-not-to-use guidance is given. An agent must infer the routing decision from the word 'one-shot' and the content list.

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

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about permissions, mutation effects, reversibility, return format, or what `open` does. The word `create` implies a write operation, but no meaningful behavioral context is supplied.

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?

The definition is a single front-loaded sentence with no filler. It is efficient, though for a four-operation, 13-parameter tool it is arguably too sparse to be fully structured.

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?

This is a complex multi-operation tool with no annotations and no output schema, so the description should explain operation routing and behavioral expectations. Instead, it provides only a one-line summary, leaving major gaps around list behavior, create side effects, open semantics, and return values.

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%, so all 13 parameters are already documented in the schema, establishing a baseline of 3. The description adds no parameter-level meaning and even omits the `list` operation that the schema exposes.

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 states specific verbs and a clear resource: searching, creating, and opening calendar events in Apple Calendar. It is distinguishable from sibling tools such as notes and reminders by resource, but it omits the supported `list` operation and does not explicitly route against alternatives.

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?

The description lists some actions but gives no when-to-use guidance, no operation-selection advice, and no exclusions or prerequisites. An agent must inspect the schema enum to discover the full operation set, including `list`.

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

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

With no annotations at all, the description carries the full disclosure burden. It implies read-style retrieval but never states whether it is read-only, whether calls have side effects, or what shape the response takes (e.g., whether check_events triggers anything server-side).

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 with no filler, and the functional claim comes first. It is efficient, though the second sentence spends its words on an implementation detail rather than clarifying the operations.

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 tool with no annotations and no output schema, the description leaves too much unsaid: what a "memory" or "starter" is, what check_events does, and what the return values look like. An agent would have to guess before invoking it.

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 required parameter, but the description never explains what get_starters, get_memories, or check_events actually return or how they differ. Although schema coverage is 100%, the enum labels are not self-explanatory, so the description is the only place that could disambiguate and it does not.

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 says it "Access[es] Member Berries memories — conversation starters and recent activities," but "Member Berries" is unexplained jargon and "Access" is not a specific verb. It never tells the agent what distinguishes this from siblings like briefing, notes, or reminders.

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?

The only usage hint is "Built-in starters work without a custom host prompt," which is a configuration note rather than guidance on when to call the tool. There is no mention of when to use this versus the sibling memory/briefing tools, and no exclusions.

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

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

With no annotations, the description carries the full behavioral burden. It discloses the default return shape for list/search, but it does not mention that create is a mutation, whether it requires permissions or confirmation, or what side effects or output create has.

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?

The description is two tight sentences with the main purpose front-loaded and no wasted text. The retrieval behavior caveat is stated efficiently.

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?

There is no output schema, so the description needs to explain returns; it does so for list/search and full-text retrieval. It omits the return behavior for create and does not cover mutation side effects, leaving meaningful gaps for a four-operation 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?

Schema description coverage is 100%, so the schema already documents all seven parameters, including operation enum values and required fields. The description reinforces the includeBody default and the get alternative, but it does not add meaningful syntax or format details beyond the schema.

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 states specific verbs (search, retrieve, create) and the resource (notes in Apple Notes / Member Berries), so the core purpose is clear. It does not explicitly differentiate the tool from siblings such as briefing or reminders, but those siblings do not cover notes.

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 gives one useful usage rule: list/search return title and snippet by default, while includeBody=true or get retrieves full text. However, it does not explain when to choose search versus list versus create, so operation selection guidance is incomplete.

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

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

No annotations are provided, so the description carries the full burden. It does not disclose that 'create', 'complete', and 'delete' are mutations, whether deletion is reversible, what permissions or Reminders.app state are required, or what 'open' actually does (UI launch vs. data read). None of this is recoverable from structured fields.

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?

A single front-loaded sentence with no filler and no redundancy. Its brevity is appropriate in form, though it is brevity at the cost of substance given the seven-operation surface.

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 seven-operation, nine-parameter dispatcher with no annotations and no output schema, the description is far too thin. It never explains the relationship between 'list' and 'listById', distinguishes 'search' from 'open', or warns that create/complete/delete modify user data.

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%, including per-parameter notes on which operation each field serves, so the baseline is 3. The description adds no parameter meaning beyond the schema, which is acceptable here since the schema does the work.

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 names a specific resource (Apple Reminders / Member Berries) and lists five verbs, so the general purpose is clear. But it is a multiplexed dispatcher with seven operations and omits 'list' and 'listById' entirely, leaving the agent with an incomplete map of what the tool can do.

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?

There is no guidance on when to use this tool versus the sibling tools (briefing, calendar, notes, memberberries), and no guidance on how to choose among the seven operations. The operation enum in the schema is the only routing signal, and the description adds nothing about sequencing or prerequisites.

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