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

The annotations declare readOnlyHint=true, but the description explicitly performs state-changing actions (turn_on, pause) and describes pausing emails. A read-only hint contradicts an on/off toggle, so per the rubric this is scored 1 and flagged. The rich behavioral detail (daily cadence, never posts, Thursday nudge, email delivery) is real and valuable, but the annotation conflict is disqualifying.

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?

The opening sentence is well front-loaded (what the tool does), but it expands into a long run-on catalog of internal daily behavior that is more than a selector needs for a toggle tool. The structure is readable but the density of tangential detail dilutes the core action.

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 return burden and does explain the observable states (on/paused/status) and side effects. It also documents the alternate entry points (Agents card, Scheduled tab, in_brand_brief → Your day). The main gap is the misleading readOnly annotation, not missing descriptive content.

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 100%, so the baseline is 3. The description adds genuine meaning beyond the schema by clarifying that posts_per_week is 0-3, governs how many posts the generated plans hold, and that 0 is Off, 'the same as pause' — a non-obvious equivalence not derivable from the enum alone.

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 states a specific verb and resource: it turns the LinkedIn manager on, pauses it, or reports its state. This is concrete and distinct from most siblings, though it never explicitly names or distinguishes itself from adjacent tools like my_linkedin_week or draft_my_planned_posts, which overlap with the 'plans the week' and 'drafts the posts' behavior it describes.

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?

It gives explicit trigger phrases ('turn on the LinkedIn manager', 'pause my LinkedIn emails', 'is my LinkedIn manager on', 'post twice a week'), which clearly signal when to invoke it. It stops short of naming alternatives or stating when NOT to use it, so it earns a 4 rather than a 5.

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