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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds genuine context beyond them: empty days are returned, cards without postedAt are omitted, UTC formatting, the default range, and the reassurance that it 'does not modify scheduled dates'.

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 tight paragraph, front-loaded with the return shape, then the placement rule, then the parameter formats. Dense but every sentence carries information; the 'same rule as the calendars in the Dalea app' clause is the only mildly expendable phrase.

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?

No output schema exists, yet the description enumerates the returned fields (id, title, status, platforms, mediaType, postedAt), so return semantics are covered. The main remaining gap is the undocumented brandId parameter, which is minor for an otherwise complete read-only tool.

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 description coverage is 0%, so the description carries the burden and does explain 'from'/'to' as YYYY-MM-DD in UTC with a stated default. However, the third parameter 'brandId' is never mentioned, leaving one of three parameters undocumented in both places.

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 ('Get the brand's content calendar') plus the exact output shape: one entry per day, empty days included, with named card fields. It also distinguishes itself from the sibling 'list_contents' by explaining which cards are excluded, so an agent can tell the two apart without opening a schema.

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?

Gives the default date window (today through next 7 days) and the rule that cards sit on their postedAt day, then routes the agent to 'list_contents' for cards with no postedAt. Clear context and a named alternative, though it never states an explicit 'use this when X' selection criterion.

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