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

Beyond the readOnly/openWorld annotations it discloses ordering (grouped dashboard, chart, dataset, then by ID within group), the no-pagination constraint, the empty-result shape (items:[]), and an auth caveat that links require Chartbrew sign-in. These are precisely the operational surprises an agent would otherwise hit at call time.

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?

Front-loaded with the verb and resource, then semicolon-separated operational clauses; almost no filler. It is densely packed and would read slightly better as short sentences, but nothing is redundant enough to cut.

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 an output schema, 100% param coverage, and readOnly annotations, the description covers nearly everything needed. The only unstated scope question is whether the search spans one workspace or all accessible ones, which matters given the tool's 'workspace' name.

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 coverage is 100%, so types/limit/query meaning is already documented; the description still adds a genuinely schema-invisible fact: the limit is a single total across all groups, not per-group. It is silent on the literal-substring and escape behavior, which the schema already covers, so 4 rather than 5.

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?

States a specific verb and resource set ('Find accessible dashboards, charts, and saved datasets by name') plus the scope qualifier 'accessible', so an agent immediately knows what is returned and where those IDs are consumed ('use returned IDs with the data and filter tools'). It contrasts itself with a sibling by naming get_workspace_activity explicitly.

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?

Gives both a use path (feed returned IDs into data/filter tools) and an alternative ('Use get_workspace_activity for recent changes'), plus a remediation rule for the failure mode ('Narrow query or types if truncated'). An agent has enough to choose between this and the sibling lookup tools without opening a schema.

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