Push lead to La Growth Machine

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

The annotations declare readOnlyHint: true, but the tool name and description indicate a write operation ('push lead'). This is a direct contradiction. The description does not address the write nature, permissions, side effects, or any behavioral traits beyond cost, failing to compensate for the misleading annotation.

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 overly long with 29 parameter lines that simply duplicate the schema. The first line is misleading, and the structure is a flat list without grouping or prioritization. It is not concise and front-loads irrelevant info.

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 tool with 29 parameters, no output schema, and contradictory annotations, the description is incomplete. It omits what happens after pushing, error handling, data constraints, and integration details. The cost mention is useful but insufficient.

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 coverage is 100%, so each parameter has a description in the schema. The description merely repeats those same descriptions without adding new meaning or clarifying relationships between parameters. The baseline of 3 is appropriate as no additional value is provided.

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 says 'Push lead to La Growth Machine' but then immediately includes an unrelated line about 'List LinkedIn employees of a company', causing confusion about the tool's actual purpose. The core action of pushing a lead is clear from the title, but the contradictory description undermines clarity.

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 provided on when to use this tool versus sibling tools. The description only mentions cost per call but does not specify prerequisites, alternatives, or scenarios where this tool is preferred or should be avoided.

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