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

Annotations already mark it as read-only and non-destructive, but the description adds valuable behavioral context: it does not contact Dreambooth, meaning it's a local/cheap operation. This goes beyond the annotations to set performance expectations.

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?

Two short sentences fully convey purpose, usage guidance, and behavioral notes without redundancy. Information is front-loaded with the core purpose.

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?

Tool is trivial with no parameters and an output schema provided, so description covers all needed context. It includes cost/behavior hints that complete the picture for safe invocation. Nothing additional is required.

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?

No parameters exist, so the description has nothing to add. Baseline of 4 applies per rubric since 0 params require no explanation.

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 states the tool checks whether a Dreambooth account is connected to the conversation and identifies which one. It distinguishes itself from sibling tool connect_account by focusing on status rather than action, making the purpose immediately obvious.

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 instructs the agent to call this tool when unsure whether to run connect_account first, providing a clear decision rule. Also notes it is cheap and read-only, reinforcing when it's safe to invoke. This directly addresses usage context and alternatives.

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