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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description's 'Read-only and not metered' corroborates rather than contradicts them while adding the non-obvious metering detail. It also discloses meaningful behavioral context beyond annotations — chief among them that posting can be 'chart_exception' with a repairs path and that a sealed chart founds owner parties on new names.

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 core purpose is front-loaded, but the bulk of the text is a dense run of field-by-field definitions (account_count, node_count, owner_disagreement_count, posting) that restate what the output schema already declares. Every sentence is informative, but several are redundant given the existing output schema.

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 single-parameter read tool with a full output schema and read-only annotations, the description is more than complete — it covers lifecycle, posting states, owner semantics, and the chart_id linkage to other tools. The only shortfall is that field-level explanations duplicate the output schema rather than adding new guidance.

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?

There is a single parameter, workspace_tag, and schema coverage is 100% — the schema already explains it as the active workspace id returned by create_workspace/list_workspaces. The description adds nothing about the parameter, so the baseline 3 applies.

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?

Opens with a specific verb and resource: 'Lists the workspace's charts, active and retired alike,' and clarifies that lifecycle status distinguishes them. It never explicitly contrasts with siblings like list_chart_accounts or create_standard_chart, but the scope 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?

'Every row exposes chart_id, the selector the other chart tools take' implicitly tells the agent this is the entry point for chart workflows, and lifecycle/posting states hint at filtering. However, there is no explicit when-to-use vs. when-not guidance or named alternative for retrieving chart details.

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