create_proposal

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

Discloses key behaviors: auto-resolution, ownership by organizer, and reliance on participant responses. Adds context beyond annotations, which only indicate mutability and non-destructiveness.

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?

Four well-structured sentences that front-load the purpose and cover essential details without redundancy. Every sentence adds value.

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?

Adequately describes the tool's purpose and lifecycle given 7 parameters (5 required) and no output schema. Mentions plan and key requirements, and explains auto-resolution, but could add more on what happens after resolution.

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 100%, but description adds meaning by explaining slot weighting, auto-resolution, and the concept of candidate slots, enhancing understanding beyond schema comments.

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-resource pair 'Create a scheduling proposal' and explains the proposal lifecycle, distinguishing it from sibling tools like 'find_meeting_time' or 'confirm_event'.

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 requirements (org-level API key, Pro plan) and describes the auto-resolution behavior. Does not explicitly contrast with similar proposal tools, but provides adequate context for typical usage.

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