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

The annotations already establish that this is a safe, idempotent read that is not destructive and can open into external context. However, the description adds real value by warning that product_selected may be an unconfirmed default and that legacy status is not ledger entitlement; both are data-quality caveats an agent could not get from the schema or annotations. It doesn't describe the response shape or whether the projects list can be large or paginated.

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 lead clause is front-loaded and efficient, but the following semicolon-separated fragments are telegraphic: 'Legacy status is not ledger entitlement; use bdk_next.commerce' takes parsing effort. It is dense but not wasteful; it just reads more like internal shorthand than an agent-facing definition.

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 and no parameters, the description carries the burden of explaining return content, and it does name the main entities while flagging two important interpretation caveats. The main omission is that it never says whether the projects collection can be large or paginated, or whether authentication 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?

The tool takes zero parameters, so the baseline is 4, but the short field is really about return semantics here. The description names several returned fields (user, projects, product_selected, legacy status), which is useful, but it does so only obliquely while explaining caveats rather than systematically describing the payload.

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?

"Read the signed-in user and their projects" gives a concrete verb and resource, and it implicitly separates this tool from bdk_projects by including account identity plus projects together. It stops short of explicitly naming bdk_projects or bdk_login as alternatives, so the distinction from siblings is inferred rather than stated.

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?

"call first" is explicit sequencing guidance, and "use bdk_next.commerce" routes a specific intent (ledger entitlement) to the correct sibling. It lacks an explicit when-not clause and doesn't say why calling first matters (for example, whether other tools depend on the returned account context).

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