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

The annotation declares destructiveHint=true, but the description describes an additive creation operation ('Create an activity'). This is a direct semantic conflict: an agent cannot reconcile 'create new record' with 'may perform destructive updates.' The endpoint and return-id details are useful, but the annotation contradiction forces a score of 1.

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?

Front-loads the core action, then required fields, linkage, return value, and endpoint in a compact structure. No sentence is wasted.

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 create tool with 11 parameters and no output schema, the description covers required fields, how to obtain lookup IDs, account/user linkage, and the return shape. Optional fields are left to the schema, which is reasonable, though the destructive annotation conflict is not addressed.

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%, so all 11 parameters are already documented. The description restates required fields and lookup sources (neon_list_properties for time zones and statuses) that the schema itself already includes, adding little new parameter meaning. Baseline 3.

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?

States a specific verb and resource ('Create an activity'), enumerates supported subtypes (call, meeting, note, task), and distinguishes itself from sibling get/update/list tools by clearly being the creation operation.

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?

Provides clear context for when to use it — logging an interaction or scheduling a task — and names required fields plus where to source lookup IDs. It does not explicitly exclude or compare to neon_update_activity, so it falls short of full when-not guidance.

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