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

With no annotations provided, the description carries the full burden. It discloses that the tool flips local flags but does not publish without Organization.discoveryConsent=true, requires the X-Org-Api-Key header, and that cron/resolver skip non-consented orgs. This goes well beyond a simple 'toggle' and provides important side-effect context.

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 detailed but front-loaded with the core action in the first sentence. Each warning serves a critical purpose, and the flow from action to limitation to consequence to auth requirement is logical. No sentence is wasted.

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?

Given the lack of annotations, output schema, and schema descriptions for the 3 parameters, the description covers all essential aspects: what the tool does, when it has no effect, who can grant consent, the auth header, and downstream behavior. It is highly complete for an agent to make an informed call.

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?

The schema has 0% description coverage, so the description must compensate. It clarifies the semantics of the `discoverable` parameter (local flag only, not actual publication) and maps `apiKey` to the required X-Org-Api-Key header. However, `orgSlug` is not explicitly described, though its purpose is inferable from the operation.

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?

Clearly states the tool's function: toggling the LIFECYCLE flags isPublic and servicialoPublished. This specific verb+resource combination distinguishes it from sibling tools like lifecycle_transition and admin_update. The consent warning doesn't obscure the primary purpose.

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 describes when this tool should not be relied upon (non-consented orgs) and names the alternative: human owner via PATCH endpoint. It also explains the consequence of using it without consent, telling the agent when to expect no publication. This is strong when/when-not guidance.

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