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

With no annotations, the description carries the full burden for behavioral disclosure. It only states the action, providing no information about duplication behavior, required permissions, optional fields, or return values. This is a bare minimum statement that adds nothing beyond the tool's name.

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 only one sentence, but this is under-specification rather than conciseness. It does not fulfill the need to explain tool behavior or parameters, and every word is essentially redundant with the tool name.

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 4 parameters, no annotations, and no output schema, the description is severely incomplete. It lacks essential context about the contact creation process, field meanings, error cases, and expected outcomes, making it inadequate for an agent to use correctly.

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 0%, so the description must compensate. It does not mention any parameters, nor does it hint at field requirements or types. The agent must rely entirely on the schema, which also lacks descriptions, leaving parameter semantics unexplained.

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 'Create a HubSpot contact' clearly identifies the action (create) and the resource (HubSpot contact), distinguishing it from SF and Outlook contact tools. However, it does not explicitly differentiate from the generic 'create_contact' sibling, so it is clear but lacks explicit scoping.

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 versus alternatives like sf_create_contact or lookup_contact. No context on prerequisites, target audience, or typical scenarios is provided.

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