list_governance_entities

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

No annotations are provided, so the description should carry the full burden of behavioral disclosure. 'List' does imply a read-only operation, which is the primary behavioral trait, but the description doesn't disclose output format, pagination behavior, ordering, or whether empty results or errors are possible. For a simple list operation with no parameters, the minimal disclosure is somewhat acceptable but still thin.

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 a single, efficient sentence with zero waste. However, it is arguably under-specified rather than concise in a useful way — it states only the bare minimum without any clarifying context, so it doesn't earn a 5.

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 tool with no parameters (0 params, complexity is low), the description is simple. It has an output schema present, which reduces the need to document return values. However, given the large sibling set including multiple list tools and governance-related tools, the description falls short on differentiating scope. It also lacks guidance that could help an agent decide when 'governance entities' is the right resource to list.

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?

The tool has zero parameters and schema description coverage is 100% (trivially, since the schema is empty). With no parameters to describe, the parameter dimension is essentially satisfied by the empty schema. The description adds no parameter information, but none is needed.

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 'List all Governance entities' uses a clear verb (list) and resource (Governance entities), but does not distinguish it from the many sibling tools. It is a minimal, clear statement but provides no differentiation from related list tools like list_components, list_repos, or list_tasks, nor from the adjacent create_governance and add_governance 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?

There is no guidance on when to use this tool versus alternatives. With 33 sibling tools including multiple 'list_' and governance-related tools, the description provides no context about what distinguishes 'Governance entities' from other entity types or when listing governance is appropriate versus searching or resolving references.

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