Create Activity

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

Annotations already indicate readOnlyHint:false, idempotentHint:false, and destructiveHint:false, and the description's 'Create' is consistent with those settings. However, the description adds no additional behavioral context such as validation rules, permission requirements, or side effects on related entities, so it does not exceed the annotations' coverage in a meaningful way.

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 a single, front-loaded sentence containing the key scoping word 'single' and no filler. It is appropriately minimal given the rich schema underneath.

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?

The schema and output schema provide strong technical coverage for the 10-parameter create operation, so return-value documentation is unnecessary. However, the description omits usage context, especially when an agent should select create_activity over import_transactions, and does not mention any account-existence or symbol-resolution constraints.

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%, with each of the 10 parameters already documented by name, type, required status, and default values. The description itself adds no parameter-level detail beyond the word 'transaction/activity', so the schema carries the full burden and the baseline score of 3 is appropriate.

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 ('Create') and resource ('single new transaction/activity'), clearly distinguishing it from read/list, update, and delete tools. It does not directly contrast with the batch-style sibling import_transactions, so it misses a bit of differentiation.

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 provides no guidance on when to use this tool versus alternatives such as import_transactions, nor does it mention any prerequisites or when not to use it. The sibling list implies alternatives exist, but the description itself leaves usage decisions to the agent.

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