get_curation

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

Description implies read-only behavior but does not disclose auth needs, error handling, or rate limits. With no annotations, the description carries the burden and is adequate but not rich.

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 efficient, using a bulleted list within a sentence. Front-loaded and clear, though slightly verbose in listing fields.

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?

Despite no output schema, description enumerates return fields comprehensively. For a simple get tool with one param, it's complete enough for an agent to understand results.

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?

Single parameter 'id' with 100% schema coverage. Description adds minimal extra meaning beyond schema (e.g., origin from search results), so baseline 3 applies.

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 it retrieves detailed info for a specific curation, listing included fields. Distinguishes from sibling search_curations by specifying post-search usage.

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?

Explicitly says 'Use this after search_curations to get full details about a specific result,' providing clear context. Does not list exclusions but is sufficient for a simple retrieval tool.

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