role_data_matrix

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

With no annotations, the description carries the full burden and does well: it flags deprecation, explains the exclusive-lock failure mode, describes per-role outcomes (read/denied/error plus http and ok flags), and warns that real role differences likely need external provisioning. It does not detail auth/permission requirements for the call itself or pagination/size limits.

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 deprecation warning is correctly front-loaded, but the body is a single dense run-on sentence packed with parentheticals, mixed scripts, and em-dash asides. It also restates the full return object even though an output schema exists, which is partly redundant.

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?

An output schema exists, so return-value detail is technically optional, and the description covers deprecation, the lock caveat, and provisioning constraints thoroughly. The main gap is the three non-roles parameters (entity_set, filter, base_url) that remain undocumented at 0% schema coverage.

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 description coverage is 0%, so the description must compensate. It does document the roles array item shape ({label, user, password} with an optional expectation {expect_access, min_count}), but entity_set, filter, and base_url are left entirely unexplained in both schema and description.

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 states a specific verb and resource: it runs the SAME data-layer read under several credentials/roles and reports per-role access plus record count. No sibling tool performs role-based access matrices, so the scope is unambiguous even before opening the schema.

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?

It gives explicit when-not guidance (deprecated for a test-client-held base under an exclusive lock, valid only against a separately published non-exclusive endpoint) and notes that genuine role differences require out-of-band provisioning via admin-mcp, outside qa-mcp's read-only scope. It stops short of naming a specific sibling tool as the in-scope alternative, so it is strong but not a full when/when-not/alternative triad.

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