connect_with_person

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

Discloses write nature, gating, possible return statuses (ok, duplicate, etc.), and quota impact. No annotation provided, so description covers key aspects, though not exhaustive (e.g., no mention of success effect).

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?

Two brief sentences with no redundancy. Front-loaded with key action and constraints. Every part earns 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?

Covers core: action, gating, returns, and rate limit. Lacks explanation of post-connection behavior (e.g., pending state), but given no output schema and no annotations, it's reasonably complete for a simple connect 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 covers all 3 parameters (100% coverage). Description adds value by explaining confirm's role as safety gate and listing possible return statuses, which are not in schema. This justifies above 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?

Clearly states 'Send a connection request' which is specific and differentiates from sibling tools like send_message (for messaging) or comment_on_post. The verb and resource are unambiguous.

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 explicit gating instruction: 'requires confirm:true' and mentions daily cap. However, lacks explicit when-not-to-use or alternatives, but context is clear for intended use.

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