pressable_add_collaborator

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

With no annotations, the description carries full responsibility for revealing behavior. It only states the action but does not disclose permissions needed, whether the operation is idempotent, what happens if the collaborator already exists, or any side effects. This is insufficient for a mutation tool.

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 a single sentence, which is concise, but it is under-specified. It omits essential information about usage and parameters, making it less a model of conciseness and more a minimal placeholder. The sentence does not earn its place by providing sufficient actionability.

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 lack of annotations and output schema, the description should compensate by explaining the tool's context and outcome. It fails to mention what the API call returns, whether it requires existing site collaboration settings, or any prerequisites. For a simple tool, it is still incomplete.

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?

The input schema has 0% description coverage, and the description adds no clarification about the parameters 'email' or 'site_id'. It does not explain the expected format, where to find the site_id, or any relationship between the two parameters. The agent must rely solely on the parameter names.

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 'Add' and the resource 'collaborator to a site', making the core action unambiguous. It distinguishes itself from the sibling tool pressable_list_collaborators, which lists collaborators, by implying the create action.

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?

No usage guidance is provided. The description does not mention when to use this tool versus alternatives, nor any prerequisites or exclusions. The agent is left to infer context from the sibling tool list, but the description itself offers no direction.

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