Things App MCP

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds value by specifying the implementation method ('Uses AppleScript') and platform restriction ('macOS only'), which are useful behavioral traits not covered by annotations. However, it doesn't detail aspects like rate limits, error handling, or response format, leaving some gaps.

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 very concise with two sentences that directly convey essential information: the tool's purpose and its implementation constraints. Every word earns its place, and it's front-loaded with the core functionality, making it efficient and easy to parse.

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?

Given the tool's simplicity (0 parameters, read-only operation), the description is reasonably complete. It covers the purpose and key behavioral constraints (AppleScript, macOS). However, without an output schema, it doesn't explain what 'areas' are or the return format, which could be helpful for an agent to interpret results, leaving a minor 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?

The input schema has 0 parameters with 100% coverage, meaning no parameters need documentation. The description doesn't add parameter-specific information, which is appropriate here. A baseline of 4 is applied since there are no parameters to describe, and the description doesn't introduce unnecessary complexity.

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 clearly states the action ('Get all areas') and resource ('from Things'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get-projects' or 'get-todos', which also retrieve data from the same system, so it misses full sibling distinction.

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 implies usage by mentioning 'Uses AppleScript (macOS only)', which provides some context about platform constraints. However, it doesn't specify when to use this tool versus alternatives like 'get-projects' or 'get-todos', nor does it provide explicit when-not-to-use guidance or named alternatives.

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