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

No annotations are provided, so the description carries the full behavioral burden. It discloses that results include a one-line summary, but says nothing about ordering, pagination, scope limits, permissions, or what "working operations" versus "requirements recorded" actually means.

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?

It is a single sentence with the list action front-loaded, so it is compact. However, the colon introduces a confusing appositive that muddles rather than clarifies the resource being listed.

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 zero-parameter list tool with no output schema and no annotations, the description should clearly define what a proposition is and what the returned one-line summaries contain. The current wording leaves the core resource ambiguous and provides no sense of result size or scope.

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 takes zero parameters, so the baseline is 4. The description does not need to explain parameter semantics.

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 says "List every service," which is a clear verb but names a resource ("service") that never appears in the tool name "list_propositions." The phrase "working operations and the requirements recorded" gestures at propositions but does not define them, so an agent cannot confidently tell what is being listed.

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 explicit guidance on when to use this tool versus the sibling describe_proposition or entity_lookup. "List every service" implies a broad enumeration use case, but the agent must infer that from an ambiguous sentence.

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