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

Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, but the description explicitly says it runs ANY BankrollSZN tool, and the sibling list includes destructive operations such as delete_testimonial. A tool that can execute destructive siblings cannot honestly be labeled read-only/non-destructive; the description contradicts the annotations.

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?

Two tight sentences, front-loaded with the core capability and followed by the discovery pointer. No wasted wording.

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 dispatcher with a fully covered 2-param schema and no output schema, the description covers what it does and how to find callable names. It misses the safety caveat that the invocation can reach destructive tools, which matters given the mislabeled annotations.

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 both 'tool' and 'arguments' are already documented in the schema. The description only reinforces that the name comes from bankrollszn_tools and does not add format or constraint detail beyond it, so the baseline 3 is 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?

States a specific verb and resource: it 'Runs any BankrollSZN tool by name with its arguments.' An agent can grasp that this is the generic dispatcher versus the specific invoke_* siblings. It stops short of explicitly contrasting with those siblings.

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 tells the agent where to find tool names and schemas (bankrollszn_tools), which implies a discovery-then-invoke workflow. However it never states when to prefer this generic invoker over the many specific invoke_* siblings, leaving that choice to inference.

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