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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) by disclosing that an email is sent to a third party, that the invitee needs a free Milanote account, that Home cannot be shared, that per-call confirmation is the default but can be turned off, and that a Cotlet API key is required. This is exactly the side-effect context an agent needs for an outward-facing action.

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?

Front-loads the core action in the first sentence, then layers prerequisites and safety notes. Dense but each sentence carries distinct information; slightly more text than strictly necessary given the annotations already flag the open-world nature.

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?

No output schema exists and none is needed for an invitation action; the description covers recipient requirements, scope of sharing, restrictions, confirmation behavior, and auth needs. Nothing an agent needs to invoke this correctly is missing.

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 100% for both parameters, and the schema already explains that board_id comes from list_boards or the board URL. The description adds only the implicit constraint that the Home board is not a valid target, so the baseline 3 applies.

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?

States a specific verb and resource (invite someone by email to edit a board and its sub-boards) plus the granted role, which cleanly separates it from sibling operations like create_board or add_note. An agent knows exactly what this does without opening the schema.

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?

Gives clear conditions and exclusions: sharing applies to sub-boards, the Home board cannot be shared, and the user must confirm before each call. It does not name an alternative tool, but no sibling covers invitation, so there is little to disambiguate against.

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