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

Annotations already declare it read-only, idempotent, non-destructive and closed-world. The description adds genuine value by disclosing what is returned (references, deliveries, URLs, optional client folder link) that no output schema communicates, though it omits how missing files are handled.

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?

One dense sentence, front-loaded with the core action and the id source, then the payload details. Slightly heavy with parenthetical role clarifications but every clause adds information.

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?

With no output schema, the description carries the burden of explaining returns, which it does thoroughly for the file/URL payload. A simple single-param getter, so it's nearly complete; error/empty cases are the only minor gap.

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 single id parameter has 0% schema description coverage, but the description compensates by specifying its meaning and origin ('by id (from list_agenda)'), telling the agent where to source it. It doesn't state the id format, keeping it short of a 5.

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+resource: retrieves one task or meeting by id, and details the payload (files, reference/delivery roles, public URLs, client folder link). It differentiates itself from list_agenda by noting the id comes from there, though it doesn't fully contrast with create/update/delete siblings.

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?

'id (from list_agenda)' implies the workflow of listing first to obtain an id, giving implied usage. But there's no explicit when-to-use versus alternatives, no when-not guidance, and no mention of behavior when the id is invalid.

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