Shortcuts Health

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

The annotations provide readOnlyHint=true and idempotentHint=true, but the description adds no behavioral context beyond that. It does not disclose what the tool returns, what 'health' means, whether it contacts external services, or how results should be interpreted. The description carries essentially none of the behavioral disclosure burden.

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 only one sentence, but it is short because it is empty, not because it is tightly informative. The boilerplate phrase 'Delegated Apple domain tool' does not earn its place—it provides no actionable information to an agent.

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?

Even for a simplified no-parameter health check, the description must explain what is being checked and what the output represents. It does neither. An agent is left to rely solely on the name and sibling patterns, which is insufficient for confident invocation.

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?

The tool has zero parameters, so there is nothing for the description to clarify. With no parameters to document, the baseline is 4, and the description's silence on this front is acceptable.

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 only identifies the tool as a 'Delegated Apple domain tool' exposed through Apple-Tools-MCP, but never states what 'shortcuts_health' actually does. The name implies a health check, but the description does not provide a verb, resource, or functional outcome. It is nearly a tautology that restates the tool's name.

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 whatsoever about when to use this tool, what conditions call for it, or how it differs from sibling tools like system_health, mail_health, or reminders_health. An agent receives no basis for selecting it over alternatives.

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