add_object_collaborator

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

Description claims idempotency when already subscribed, but annotation 'idempotentHint' is false, creating a contradiction. No other behavioral traits disclosed beyond what annotations imply.

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?

Two concise sentences with front-loaded purpose and essential details. No wasted 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?

Captures core functionality, member specification, and idempotency. Output schema exists, so return values are covered. Lacks explanation of object identification parameters but schema documents them.

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?

High schema coverage (86%). Description adds value by summarizing accepted member formats, compensating for the schema's complexity. Other parameters are adequately documented in schema.

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?

Clearly states the verb 'Subscribe' and resource 'object notifications by adding a core collaborator row'. Distinguishes from siblings like 'remove_object_collaborator' and 'subscribe_to_object_notifications' by specifying the mechanism.

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?

Provides explicit guidance on member specification (UUID, name, or email) and notes idempotency. Lacks explicit when-not-to-use or alternatives, but context is clear.

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