list_entities

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Browse' and 'Filter by kind', but does not disclose aspects like pagination, rate limits, or whether the operation is read-only. Given the lack of annotations, this is insufficient.

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 very short (one sentence). While it avoids wordiness, it could be more informative without losing conciseness. It adequately front-loads the core purpose but omits useful detail.

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?

Given no output schema and no annotations, the description should explain return structure, pagination, or filtering mechanics. It fails to do so, leaving significant gaps for an agent to determine correct invocation.

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%, yet description only mentions 'Filter by kind' without explaining valid values or behavior. The 'limit' parameter is not discussed. This adds minimal meaning beyond the raw schema.

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 clearly states it browses the BCA entity universe with a specific scope (~200 entities) and indicates filtering by kind. This verb+resource+scope effectively distinguishes it from siblings like get_entity (individual entity) and other list tools.

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?

The description implies usage for browsing and filtering entities, but it does not provide explicit guidance on when to use this tool versus alternatives like get_entity or search tools. No exclusions or prerequisites are mentioned.

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