get_discover_curation_options

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

Annotations already cover read-only and idempotency. The description adds meaningful behavioral context beyond annotations: the 'host-only' access restriction and the fact that it returns settings rather than actual discover-page info. This helps the agent understand auth requirements and semantic scope.

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 two sentences, front-loaded with the core purpose, and every phrase adds value. The sibling distinction is concise and does not waste 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?

For a read-only getter with a simple two-parameter schema and output schema present, the description fully explains the tool's role, its host-only nature, and how it fits among related tools. No critical information is missing.

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 100%, so the baseline of 3 applies. The description does not add any additional parameter-specific meaning; the event_id and fields parameters are adequately documented in the schema. No further compensation is needed.

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 ('Get') and the resource ('discover-page curation options for a hosted Partiful event'), and explicitly distinguishes the tool from two sibling tools (get_event_discover_info and get_event_discover_status), making its purpose unambiguous.

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 provides clear context by noting the tool is 'host-only' and refers to 'host-side settings', which implies when it should be used. It also differentiates from two related tools, but does not explicitly state 'use this instead of X when Y', so it falls short of full explicit exclusions.

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