monica_activity

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

No annotations provided. Description discloses delete is irreversible, which is a key behavioral trait. However, it does not mention any other constraints, authorization needs, or 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?

Extremely concise: two sentences with no wasted words. Front-loads the action list and the critical warning about delete irreversibility.

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?

Despite 10 parameters and no output schema, the description provides minimal context. It does not explain how to use parameters for different actions, what the response looks like, or dependencies. For a CRUD tool with many parameters, more guidance is needed.

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%, so each parameter has a description. The tool description adds value by explaining the action parameter's semantics (e.g., list = paginated) and warns about delete. This elevates from baseline 3 slightly.

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?

Clearly states the tool manages activities with specific actions (list, get, create, update, delete). This distinguishes it from sibling tools like monica_activity_type and monica_contact.

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?

Lists the actions and warns about delete irreversibility, but does not explicitly guide when to use this tool versus alternatives (e.g., monica_activity_type). Usage is implied by resource type.

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