solidtime_member_invite_placeholder

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the mutation profile is largely covered. The description adds the dry-run escape hatch and the underlying endpoint, but says nothing about whether an email is dispatched, what state the placeholder ends in, or whether the call is reversible — useful extras the annotations cannot supply.

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 sentences, front-loaded with the effect of the call before the HTTP detail and the dry-run caveat. The endpoint path earns its place as a concrete aid, and there is no filler, though the writing is telegraphic rather than fully explanatory.

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 four-parameter mutation tool with no output schema and non-idempotent semantics, the description is thin: it omits what the response contains, what happens to the placeholder record and any existing data, and whether the invited email address replaces the placeholder's identity. An agent would have to guess at the operation's side effects.

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 only 50%: confirm and organization_id are documented in the schema, while the two required parameters, member_id and email, have no description anywhere. The tool description does not compensate at all — it never mentions what member_id refers to (placeholder member UUID?) or what the email argument does to the existing member record.

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 gives a concrete verb and resource: it converts a placeholder member into a real member via invite-placeholder. That clearly separates it from siblings like solidtime_member_make_placeholder (the reverse direction), though it never names those siblings explicitly.

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 only usage guidance is the conditional 'Omit confirm for a dry-run', which is a parameter instruction rather than a rule for choosing this tool over alternatives. There is no statement of prerequisites, no mention of when the member must already be a placeholder, and no routing to sibling tools.

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