Attach an assignee

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

No behavioral details beyond the action. Does not disclose side effects, error conditions, or what happens to existing assignees. With no annotations, the description carries the full burden but provides minimal info.

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 very short, but it sacrifices necessary detail. It is not efficiently conveying essential information; it's underspecified.

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 (nested objects, no output schema, no annotations), the description is incomplete. It does not explain the tool's role in the CRM domain or what 'attach' means operationally.

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%, and the description does not explain the parameters. It only notes 'Body: application/json' but gives no meaning for assigneeId or dealId, leaving the agent to rely solely on the schema with no added context.

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 states 'Attach an assignee' and provides the endpoint, making the verb and resource clear. However, it does not differentiate from sibling tools like 'weeek_add_assignees' which may serve a similar 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?

No guidance on when to use this tool versus alternatives. No mention of prerequisites, contexts, or when not to use it.

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