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

The description adds meaningful behavioral context beyond the readOnlyHint annotation by stating 'mttr writes no post and posts nothing; you or your person write them.' It also explains the brief contents, including character counts and how X counts links. It does not cover auth or rate-limit behavior, but it is strong for a read-only tool.

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 description is compact and front-loads the core resource before listing brief contents. The first sentence is dense and run-on, but every clause contributes information about the returned briefs or the no-posting behavior.

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 what comes back, and it does so by listing the brief fields for X and LinkedIn. It also clarifies that no post is written, which is important for invocation expectations. A minor gap is that it does not describe the response shape or whether multiple briefs are returned.

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 schema already defines both required parameters and the live-page prerequisite for 'brief'. The description does not add syntax or formatting detail beyond what the schema provides, so the baseline of 3 is appropriate.

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 identifies the returned resource precisely: briefs for X and LinkedIn posts about a page that went live from a content brief. It is not just a restatement of the title, but it never names a sibling tool such as mttr_content_next or mttr_content_done, so differentiation is left implicit.

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?

Usage is implied by the phrase 'about a page that went live from one of your content briefs', which tells the agent this applies after a brief's page is live. However, there is no explicit when-not guidance and no alternative tool named for related cases.

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