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

Annotations are empty, so the description must disclose behavior. It only says 'Help for bluesky-mcp,' which does not communicate what happens (e.g., returns a help message, lists tools, side effects, safety profile). No behavioral traits are disclosed, making the tool a black box.

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 entire description is a seven-word fragment. While it is short, it is under-specified rather than concise; it reads as a placeholder. It does not earn its place because it conveys almost no information.

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 tool's simplicity (no params) and the presence of an output schema, the description still fails to provide enough context. It does not state what help is offered, whether it is safe/read-only, or how it relates to sibling tools. The agent cannot confidently invoke this tool based on this description alone.

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 tool has zero parameters, so the baseline is 4. The schema description coverage is trivially 100%, and the description correctly avoids adding parameter details that don't exist.

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 'Help for bluesky-mcp' is essentially a restatement of the tool name without specifying a clear action or what the help contains. It lacks a specific verb and resource, and does not differentiate from siblings beyond being a generic help entry. This is closer to a tautology than a purposeful description.

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?

The description gives no guidance on when to call this tool versus alternatives like bluesky_shutdown or bluesky_social_tool. There is no mention of context, prerequisites, or exclusions. The agent receives no decision-relevant usage information.

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

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

The description adds a valuable behavioral detail beyond the tool name: 'process exit left to host.' This clarifies that the tool only signals shutdown and does not terminate the process itself. With no annotations, this disclosure is meaningful, though it does not address other potential side effects.

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 a single sentence that front-loads the action ('Signal graceful shutdown') and adds the key qualifier about process exit. Every word earns its place, with no redundancy.

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 tool's simplicity (no parameters, no annotations), the description is nearly complete. It covers the essential behavior, and the output schema presumably handles return values. The lack of usage guidance is minor but not a significant gap for such a straightforward 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?

The tool has zero parameters and an empty schema. The description naturally provides no parameter information, but the zero-parameter baseline of 4 is appropriate since there is nothing to explain.

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 clearly identifies the tool as signaling a graceful shutdown, with a specific verb ('signal') and resource ('graceful shutdown'). It is distinct from sibling tools like bluesky_help or show_outbox_card, which serve different purposes.

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?

The description implies usage (call when you want a graceful shutdown) but provides no explicit context, prerequisites, or alternatives. There is no stated when-to-use or when-not-to-use guidance, making it acceptable but not explicit.

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

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

Annotations are empty, so the description carries the full burden of behavioral disclosure. It only provides a vague return format ('dialogic dict') and a few examples, without addressing side effects, authorization, rate limits, or error handling. The 'fleet drafts' note is a workflow clue but doesn't reveal operational traits like whether operations are destructive or read-only.

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 short but poorly structured; the 'Portmanteau' opener is cryptic and wastes the front-loaded position. The return format section is clear but too generic, and the examples are helpful yet insufficient. The overall content is concise in volume but not in usefulness, with jargon like 'dialogic dict' adding confusion.

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 13 parameters, no annotations, and only a vague return format, the description is far from complete. It doesn't enumerate possible operation values, explain output schema, or cover use scenarios beyond the outbox example. The tool's complexity demands a much more detailed description to be usable by an AI agent.

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 must compensate for parameter semantics. It only references operation and status_text in examples, leaving 11 parameters unexplained. While names like media_path and visibility are intuitive, their constraints, defaults, or interactions with operations are not described, and payload is entirely opaque.

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 opens with 'Portmanteau: post/timeline/outbox_*' which hints at a multi-operation dispatcher but never states a clear verb+resource purpose. The examples show operation=outbox_list, notifications, and outbox_enqueue, but no overarching statement like 'perform Bluesky social actions'. This leaves the tool's core function ambiguous and fails to distinguish it from siblings other than by implication.

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?

The only usage hint is 'fleet drafts use outbox_enqueue → approve → publish', which describes a specific workflow but doesn't explain when to choose this tool over alternatives like bluesky_help or show_outbox_card. There are no decision criteria for selecting operations, and no exclusions or alternatives are mentioned. The guidance is minimal and not actionable for an agent.

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

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

With empty annotations, the description carries full responsibility for behavioral disclosure. It only states that the tool 'summarizes pending outbox drafts', but it does not indicate whether this is a read-only operation, if it has side effects, or what the output format is. The lack of behavioral details is a significant gap for a tool that likely consumes UI resources.

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 a single, concise sentence that gets to the point. However, the phrase 'Rich Prefab card' is not self-explanatory and adds slight ambiguity, preventing a perfect score. Still, it is efficiently worded with no waste.

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?

Despite having an output schema, the description is minimal and fails to provide context about what 'pending outbox drafts' are, what 'Rich Prefab card' means, or when the tool should be used. Given its simplicity, some context might be assumed, but the description alone is insufficient for an AI agent to fully understand the tool's role in a larger workflow.

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 tool has zero parameters, which earns a baseline score of 4. The input schema is empty, so there are no parameter details to explain. The description does not need to add parameter semantics, and the 100% schema coverage is vacuous.

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 'Rich Prefab card summarizing pending outbox drafts' clearly states the tool's function: to display a card summarizing pending outbox content. It uses a strong verb ('summarizing') and a specific resource ('pending outbox drafts'), distinguishing it from sibling tools like bluesky_help and bluesky_shutdown. The term 'Prefab' is somewhat jargon, but the core purpose is unambiguous.

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?

No usage guidance is provided. The description does not explain when to use this tool versus alternatives, nor does it mention any prerequisites or contexts. Users are left to infer that this is for viewing outbox drafts, but there is no explicit direction.

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