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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds value by enumerating returned content categories, including live approval receipts, dependencies, partial successes, and continuation controls, but it does not explain pagination, cost, auth requirements, or how those artifacts should be interpreted.

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 front-loaded sentence that immediately states the action and resource. It is efficient, though the trailing list of opaque nouns is dense and could be reorganized for faster comprehension.

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?

For a zero-parameter read tool with rich annotations but no output schema, the description gives some sense of what is returned but leaves key gaps: what a business plan contains, whether results are paginated, and how this differs from open_business_workspace are unaddressed. It is minimally adequate but not fully complete.

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 there are no parameter semantics for the description to clarify. The schema is correspondingly empty and fully covered, making the baseline of 4 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 uses a clear verb, "Read," and names the resource: "this connection's persisted business plans" plus specific related artifacts such as live approval receipts, dependencies, and continuation controls. It is much more specific than a tautology, but it does not distinguish this tool from the related sibling open_business_workspace or clarify what a "business plan" is in this system.

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 "Read this connection's persisted business plans," but there is no explicit statement of when to use this tool versus alternatives such as open_business_workspace or other read-oriented sibling tools. The context is enough to infer a read operation, but it does not provide real selection guidance.

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