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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description adds real semantic value by explaining that `configured: false` means no custom grid and Ignix default slots apply. It does not discuss auth/permission requirements or error behavior, which keeps it below a 5.

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?

Front-loaded with the core action and return shape, then fallback semantics, then the mutation alternative. Dense but every sentence carries information; the inline field enumeration and backticked identifiers are efficient rather than padded.

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 read-only, single-optional-parameter tool with no output schema, the description supplies the return shape, timezone semantics, the configured=false fallback, and the mutation counterpart. Nothing an agent needs in order to call it correctly or interpret the result is missing.

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% and the single workspaceId parameter is fully documented in the schema, including the fallback when the connection is tied to one workspace or an account is supplied. The description only alludes to workspace scoping ('one workspace', 'each workspace has its own') without adding format or resolution detail beyond the schema, so baseline 3 applies.

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 ('Read the weekly posting grid of one workspace') and immediately enumerates the returned fields (weekday, day, hour, minute) in the organization timezone. This is clearly distinguishable from set_posting_queue (write) and from sibling read tools like get_posting_cadence or get_best_times.

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?

Explicitly names the alternative for mutation ('To change it use set_posting_queue, which replaces the whole grid') and explains downstream consumers (useQueue in create_post, recycle_post, suggest_publish_times). It also clarifies the per-workspace scoping that an agent must know before calling.

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