solidtime_invitations

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is largely covered. The description adds the confirmation requirement ("Writes need confirm"), which is genuine behavioral context, but it never says what removal actually destroys (e.g., invalidating an outstanding invite link) or whether resend supersedes a prior token.

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?

Three short front-loaded fragments with zero filler; the resource comes first and the action list second. It is terse to the point of being telegraphic, 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 six-parameter, four-action tool that performs destructive writes with no output schema, the description is too thin. An agent still has to infer per-action required fields, the meaning of the empty-object dry-run behavior, and what each action returns.

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 only 33% — email, role, and invitation_id carry no descriptive text — and the description does nothing to compensate; it merely restates the action enum. Crucially, it never maps parameters to actions (invite needs email/role, remove/resend need invitation_id), which is the main semantic gap for a multi-action tool.

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?

"Organization invitations" names the resource and the description enumerates the four operations (list, invite, resend, remove), so the tool's scope is clear at a glance. It stops short of distinguishing itself from nearby siblings such as solidtime_members_list or solidtime_member_invite_placeholder, which an agent could plausibly confuse with 'action: list' or 'action: invite'.

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?

"Writes need confirm" implies the split between the read action (list) and the three mutating actions, which is useful routing guidance. However, there is no explicit when-to-use vs. the member-invite placeholder or members_list siblings, and no stated prerequisites such as required role or admin permission.

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