Apple Detect Digest Folder

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

Annotation Contradiction: readOnlyHint=true declares a read-only operation, but the description says 'persist it if found,' which describes a state-changing side effect. This directly conflicts with the annotation and misleads the agent about whether calling the tool mutates state.

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 sentence that front-loads the primary verb and delivers both the detection scope and the persistence behavior with no wasted words. Every element 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?

For a zero-parameter tool with an output schema, not much is needed, but the description leaves important behavior underspecified: what 'persist' means (where the preference is stored), what happens when no folder is found, and whether repeated calls overwrite. The read-only contradiction further compounds the incompleteness.

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?

With zero parameters, there is nothing the schema or description could mis-specify, so the no-parameter baseline of 4 applies. The description correctly avoids inventing parameter details that do not exist.

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 a specific verb ('Detect') and resource ('preferred Notes folder for daily and weekly digests'), with an added action of persisting the result. It is clear what the tool targets, but it does not differentiate from the closely related siblings apple_set_digest_folder and apple_ensure_digest_folder, so it stops short of a 5.

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 nearly identical digest-folder siblings (apple_set_digest_folder, apple_ensure_digest_folder). The description implies a purpose but provides no conditions, exclusions, or alternatives, leaving the agent to guess when 'detect and persist' is the right choice.

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