connectif_contact_fields

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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It reveals nothing about side effects, permissions, request/response format, or error behavior. The mention of 'action' conflicts with the empty schema, creating confusion rather than transparency.

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 short, but the first sentence is generic boilerplate, and the second sentence adds a misleading directive. Conciseness requires clarity, not just brevity; this text does not earn its place.

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 has no schema parameters, no output schema, and appears among many similar siblings, the description is wholly inadequate. It fails to explain what the tool does, how to invoke a specific operation, or what results to expect.

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 zero parameters, and description coverage is vacuously 100%. However, the description references an 'action' parameter that does not exist in the schema, actively misleading the agent. This is worse than providing no parameter info.

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 phrase 'Direct Connectif API operations' is generic and does not specify a concrete action (e.g., list, update, delete). 'for contact_fields' names the resource, but the siblings (connectif_contacts, connectif_purchases, etc.) follow the same pattern, so this description does not distinguish the tool. The instruction 'Use action to select an official operation' hints at a wrapper but does not clarify the actual purpose.

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?

There is no guidance on when to use this tool vs. its siblings. No context, prerequisites, or alternatives are mentioned. The vague 'Use action' line is not actionable because the schema has no 'action' parameter.

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