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

With no annotations, the description carries the full burden. It does disclose a real prerequisite ('Requires Nova API key in AR Settings') and the extraction pipeline, which is genuine added context. It omits whether a new calendar or row is created, whether the operation is asynchronous (siblings like get_research_status suggest polling patterns), and what happens on failure.

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?

Two short sentences, front-loaded with the action and target, followed by the prerequisite. No filler, no restatement of the name.

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 4-parameter mutation-style tool with no annotations, no output schema, and 25% schema coverage, the description is thin. It leaves unclear what 'calendar draft' means concretely, whether an asset/row is created, how import_notes and import_title are used, and whether the call is async.

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 coverage is only 25%: only notification_message is documented in the schema. The description adds one useful constraint on import_url ('public webpage'), but says nothing about import_notes or import_title, so two of four parameters remain fully undocumented.

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?

States a specific verb (import) and resource (a public webpage into a calendar draft), plus the mechanism (Nova extract + LLM). This distinguishes it from siblings such as import_content_calendar_json or create_calendar_row. It stops short of naming which calendar the draft lands in, leaving some ambiguity.

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?

Usage is only implied: you have a public URL and want it turned into a calendar draft. There is no explicit when-to-use vs. when-not guidance and no routing to alternatives like import_content_calendar_json or create_calendar_row, even though both appear in the sibling set.

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