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

With no annotations, the description must disclose behavior itself. It implies a read-only get operation ('drafted from...') but does not state side effects, failure modes (e.g., missing brief), or permission requirements. The output is described, but edge-case behavior is omitted, making it minimally transparent.

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, well-structured sentence that front-loads the tool's purpose and lists the output components. No wasted words or redundant 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?

For a simple get tool with one optional parameter and no output schema, the description adequately conveys the expected return (lead, headlines, link). It does not cover error scenarios, but given the simplicity and available schema, this is a 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?

Schema coverage is 100%, so the baseline is 3. The description does not mention the date parameter or its default behavior, but the schema already fully documents it as optional with a YYYY-MM-DD format and default to the most recent edition. The description adds no additional parameter context.

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 tool retrieves a LinkedIn-ready post derived from the day's sent brief, specifying its contents (lead, headlines, link). This distinguishes it from siblings like get_blog_post or get_daily_briefing, which serve different content types.

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 implies the tool is for LinkedIn posts but does not explicitly state when to use it over alternatives like get_blog_post or get_weekly_digest. No when-not-to-use guidance or alternative routing is provided, leaving the agent to infer based on the LinkedIn-specific wording.

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