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

Annotations give no safety hints; the description does not clarify whether 'funnel' reads or writes the funnel stage. Ambiguity about side effects, with no explanation of what happens to the contact.

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?

Description is moderately sized with bullet points, but includes redundant actions (get/upsert) that do not belong to this tool. Could be more concise by focusing only on funnel.

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 complexity of multiple potential actions, lack of output schema, and zero schema coverage, the description is insufficient. It does not explain return values, error conditions, or the effect of the funnel action.

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 has 0% description coverage. The description explains identifier and identifier_type for identification but does not clarify which parameters apply to the 'funnel' action (e.g., whether 'fields' is needed). Incomplete semantic mapping.

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 mentions three actions (get, upsert, funnel) but the tool name and flattened action indicate it's specifically for 'funnel'. This confuses the tool's purpose with sibling tools rdstation_contacts_get and rdstation_contacts_upsert.

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?

No guidance is given on when to use this tool versus the sibling get/upsert tools. The description lists all actions without explaining which is appropriate or how to choose.

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