share_space

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

Description adds return value info (JSON with share token and join URL) beyond annotations (destructiveHint: false). It confirms a non-destructive operation and provides expected output format.

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?

Description is extremely concise: 3 sentences plus structured Args/Returns. Front-loaded with purpose and constraint. No unnecessary 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?

Covers all essential aspects: purpose, requirement (cloud), all parameters (including defaults), and return value. For a 3-param tool with no enums, this is complete.

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 has 0% description coverage but the description explains each parameter: tag, email, permission (with default and allowed values). This adds significant value beyond the schema's bare field 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?

Description clearly states sharing a space/tag with another user by email. Distinguishes from sibling tools like create_space, delete_space, update_space, which are about management, not 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?

Provides a clear constraint: 'Requires Novyx Cloud — not available in local mode.' However, it does not explicitly guide when to use this tool over alternatives or when not to use it aside from the cloud limitation.

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