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

Annotations already carry readOnlyHint:false and destructiveHint:true, and the description's "assign" verb is consistent with a write operation — no contradiction. The description adds value beyond annotations by disclosing the approval flow (first use may require manager's approval, approval scoping semantics), but does not elaborate on what the destructiveHint entails (e.g., whether prior assignments are overwritten).

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 core purpose is front-loaded in the first sentence, with identification methods following. The bracketed approval note is verbose but earns its place by conveying critical operational rules about approval modes and not re-asking in chat; it could be tightened but nothing is wasted.

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 4-parameter tool with 100% schema coverage, annotations, and no output schema, the description covers the essential action, identification options, and the approval flow. Gaps remain: it does not describe what a successful response looks like or what destructive effect assignment has on existing triage state, though annotations mitigate the safety concern.

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 the schema fully documents all four parameters. The description restates the idea_identifier options (content snippet, ID, newest/latest) but adds little meaning beyond what the schema's parameter descriptions already provide; the one-or-more-companies phrasing weakly echoes workspace_ids.

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?

"Assign an idea to one or more companies" is a specific verb+resource statement that clearly distinguishes this tool from siblings like capture_idea (creating ideas) and delete_idea (removing ideas). The identification-method clause adds operational clarity without ambiguity.

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?

The purpose statement implies when to use the tool — whenever an agent needs to assign an existing idea to companies — but there is no explicit when-not-to-use guidance or mention of alternatives. The approval note gives invocation guidance (call on first clear ask, don't re-ask) but not tool-selection guidance relative to siblings.

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