share_create

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

No annotations provided, so the description carries the full burden. It discloses that it creates a share and requires admin authentication, and gives the date format. However, it lacks details on side effects, error conditions, or what the return value contains (though an output schema exists).

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?

Three short sentences deliver all essential information without any unnecessary words. The purpose is stated first, followed by key usage details.

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 tool has 6 parameters (1 required) and an output schema, the description covers the core creation action, authentication, and conditional parameter usage. It does not explain the output format (but output schema exists) or error handling, which is acceptable for a creation tool with an output schema.

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 only 33% (share_type and permissions have descriptions). The description adds crucial meaning: it explains that share_with is required for user/group shares and specifies the expire_date format (YYYY-MM-DD). This compensates for missing schema descriptions on two parameters.

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 'Create a share via OCS', which is a specific verb and resource. It distinguishes from sibling tools like share_delete and share_list by focusing on creation.

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 mentions the authentication requirement ('Authenticated as the admin user') and provides conditional guidance: 'For user/group shares (type 0/1), provide share_with'. However, it does not explicitly state when not to use this tool or compare with alternatives.

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