create_share_mediaitem

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

Annotations already convey readOnly=false, idempotent=true, destructive=false, and the description does not contradict them. But it adds little behavioral context beyond 'create or act on' and the schema-discovery directive; it never describes auth requirements, persistence effects, error behavior, or what a successful call changes.

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 compact and front-loaded: purpose line, endpoint, then the argument note. No filler is present, though the wording could be sharper if it replaced 'or act on' with the actual behavior.

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?

For an opaque-body POST with an output schema and supporting annotations, the description covers the essential discovery loop needed to form a payload. It remains incomplete about the operation's intended use and its relationship to the other share endpoints, leaving an agent to guess whether it creates, updates, or performs another action.

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 schema provides only an open `body` object with 0% property coverage, so the description's identification of `body` as the request payload and its pointer to the matching GET or `/schema` endpoint are useful compensating guidance. That still stops short of documenting actual fields or constraints, leaving the agent to discover them dynamically.

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 names the resource ('share mediaitem') and includes the endpoint, so an agent can infer a creation/action operation. However, 'Create or act on' is vague—it does not define what 'act on' means or what effect the POST has—and it merely restates the tool name without differentiating it from related share endpoints such as delete_share_mediaitem_by_id or get_public_share_by_slug.

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?

There is no guidance about when to use this tool versus alternatives. The only contextual instruction ('Read the matching GET or the /schema endpoint first') concerns payload construction, not tool selection, and no exclusions or sibling comparisons are given.

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