share_calendar

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

With no annotations, the description must disclose behavioral traits. It does not mention whether sharing replaces existing ACLs, sends notifications (though a parameter exists), requires authentication, or has destructive effects. The parameter 'send_notifications' is listed but its effect is not explained.

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 concise, front-loaded with the core action, and lists param details efficiently. However, the param list could be better formatted for readability.

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?

With 7 parameters, no output schema, and no annotations, the description is insufficient. It does not explain overall behavior (e.g., adding vs updating ACLs), return value, or error conditions. Context signals confirm low completeness.

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 0%. The description adds meaning for 'role', 'scope_type', and 'scope_value' with allowed values and usage note, but fails to explain 'calendar_id', 'send_notifications', 'account', and 'password'. Given low coverage, the description does not compensate enough.

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 'Share a calendar' which is a specific verb and resource. It distinguishes from create/delete/update operations by name, but does not explicitly differentiate from 'update_acl' which also modifies calendar sharing.

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 description provides allowed values for 'role' and 'scope_type', and hints at when to omit 'scope_value', but lacks guidance on when to use this tool vs alternatives like 'update_acl' or 'list_acl', and no prerequisites or context are mentioned.

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