Create a company invite

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

Annotations indicate readOnlyHint=false, idempotentHint=false, destructiveHint=false, establishing a write operation with potential side effects. The description adds the authorization class ('board') and the exact HTTP method/path. Beyond that, it does not disclose key behavioral traits (e.g., whether invites trigger notifications, if they are reversible, or what the response contains).

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 short (two sentences) and front-loads the purpose. However, it sacrifices completeness for brevity; critical parameter details and usage context are omitted, making it less effective than a slightly longer but more informative description.

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 nested parameters and an output schema, the description is far from complete. It fails to explain the meaning of the body fields, the purpose of each parameter, or what the response represents. The agent would struggle to invoke this tool correctly without external knowledge.

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 input schema has 0% description coverage, and the description provides no explanation of the parameters (body fields like humanRole, agentMessage, allowedJoinTypes). The agent has no guidance on how to populate these fields or what values are valid.

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 title and description clearly state 'Create a company invite', indicating the action (create) and resource (company invite). The description also provides the exact endpoint, distinguishing this creation operation from related list/read operations like pc_get_companies_by_company_id_invites. However, it does not elaborate on what an invite represents or the scope of the creation.

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 is provided on when to use this tool versus alternatives such as join requests or revoking invites. The agent is not told under what circumstances to create an invite or how it differs from similar actions.

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