taskhub_project_invite

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly indicates an action (invite) which typically mutates state, but it does not disclose side effects such as whether the invited user is notified, whether an invitation must be accepted, or whether the tool fails if the email already exists. It also doesn't describe access requirements or duplicate handling. This is a moderate gap for a mutation tool with no annotations.

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 a single, concise sentence that immediately states the action and target. It is front-loaded and has no superfluous words, making it efficient for an agent to parse.

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's simplicity (3 flat parameters, no output schema) and 100% schema coverage, the description is mostly sufficient. However, it lacks important contextual details: whether the invited user already needs an account, what happens if the invite is a duplicate, and whether the tool requires authentication or specific permissions. These are common gaps for an invitation tool and would benefit from elaboration.

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?

The schema has 100% coverage of parameters, each with a description (role, email, projectId), so the baseline is 3. The description adds minimal extra meaning beyond what's already in the schema: it states the email is used for the invite, which is somewhat redundant. It does not clarify the default role behavior beyond 'member' as in the schema, so it does not compensate for any gaps.

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 verb 'invite', the resource 'project', and the mechanism 'by email', which precisely defines the tool's function. It is immediately distinguishable from sibling tools like taskhub_org_invite (org-level) and taskhub_project_members (viewing existing members), as it focuses on inviting a user to a specific project via email.

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 description implies that this tool is for inviting users to projects, which is a common pattern, but it does not explicitly state when to use it over other tools like taskhub_project_members (for viewing members) or taskhub_org_invite (for org-level invites). The context of the siblings is helpful but the description itself does not provide explicit exclusions or alternatives.

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