netintel_calendar

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

With no annotations, the description carries the full behavioral burden and does well: it discloses escaping, line folding, timed vs all-day handling, and a deterministic UID enabling idempotent re-import — a genuinely useful behavioral trait. It falls short of explaining the return shape (ICS text vs file/link), which matters for a no-output-schema tool.

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?

A single front-loaded sentence packs the format, capabilities, and benefit efficiently with no filler. The trailing ellipsis and mid-clause truncation ('Google, Apple…') slightly blunt the finish but the core statement is tight.

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 nine-parameter tool with no annotations and no output schema, the description covers the conversion behavior well but leaves the parameter contract largely unexplained. An agent knows what it produces but not how to format most of the inputs.

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 0% across nine parameters, so the description must compensate — and it barely does. Only the all-day concept is indirectly echoed; nothing explains starts_at/ends_at formats, timezone handling, the 'url' field, or organizer/description semantics, leaving most inputs undocumented anywhere.

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 and resource — 'Turn event fields into a valid RFC 5545 .ics calendar file' — which is unmistakable and clearly distinct from the extraction/classification siblings. The mention of timed/all-day handling and RFC 5545 formatting sharpens what the tool actually produces.

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 trailing 'so agents can publish events that import cleanly into Google, Apple…' implies the use case (publishing events), but there is no explicit when-to-use vs an alternative, and no routing guidance relative to netintel_event_extract or netintel_event_classify. Usage is inferable but not stated.

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