othos_project_assign_member

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

No annotations provided, so description bears full burden. It says 'assign' (a write operation) but does not disclose side effects (e.g., whether it's additive or replaces existing assignments), permission requirements, or idempotency. Minimal behavioral disclosure.

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?

A single sentence is concise, but it lacks structure. It is not front-loaded with key details; it simply states the action. While brief, it misses opportunities to prioritize critical information.

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 tool has 2 UUID parameters, no output schema, and no annotations, the description is incomplete. It does not cover prerequisites, return behavior, or error cases. For a simple assignment tool, it is minimally adequate but lacks completeness.

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 description must compensate. It does not explain projectId or memberId beyond their names. The agent gains no additional meaning about what constitutes a valid member or project.

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 clearly states the action 'assign an existing member to a project' with a specific verb and resource. It distinguishes from sibling tools like 'othos_project_unassign_member' and 'othos_ticket_assign_member', though it could be more precise about what 'existing member' means.

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, prerequisites (e.g., member must exist in system, project must exist), or when not to use. The description lacks context about checking current members via 'othos_project_members' first.

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