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

Discloses mutation behavior (creating submission), consent to deal terms, and approval workflow. Adds value beyond annotations by detailing the approval process and consent implications.

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 concise sentences front-loading the primary action and optionality, then covering preconditions and requirements. No redundant words.

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 complexity (nested object, no output schema), the description adequately covers operation, prerequisites, consent, and approval. Lacks return value hints but sufficient for the submission use case.

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?

With 0% schema description coverage, the description partially compensates by explaining the required 'event_id' and 'community_id', the optional 'booking' object with its fields, and the meaning of certain parameters. However, it omits explanation of 'visibility' enum.

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 'submit' and the resource 'event to community calendar', with optional booking. It differentiates from siblings by mentioning the booking option and referencing 'find_open_slots' for slot searching.

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?

Specifies user roles ('Member or active-deal partner') and approval conditions ('await approval unless you manage the community'), providing clear context for when this tool is applicable.

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