list-sections

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

No annotations are provided, but this is a simple list/read operation with no parameters, so the behavioral burden is low. The description conveys it's a non-mutating enumeration operation. It doesn't describe output format, but with no output schema and a simple listing purpose, the risk window is minimal.

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?

One single sentence with zero waste. Every word earns its place, and it fully conveys the purpose in minimal text.

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, no-annotation discovery/enumeration tool, the description is mostly adequate. However, it doesn't mention what the output looks like (list of section names?) or how an agent might use the result (e.g., to decide which section getter to call next), which would strengthen its utility for an agent orchestrating across the sibling tools.

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 (schema coverage 100% trivially), so for a 0-param tool the baseline is 4. No parameter semantics are needed since there are no parameters to describe.

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 the tool lists profile sections retrievable by the DCR engine. The verb 'List' plus the resource 'profile sections' and the scoping 'that the DCR engine can retrieve' is specific. It distinguishes from siblings like get-skills/get-projects which retrieve actual section content, whereas this returns the section list.

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?

No explicit when-to-use or when-not-to-use guidance is provided. There's no mention of how this differs from the sibling tools beyond implicit context. The description implies it's useful for discovering available sections, but doesn't state that explicitly or suggest it as a discovery/preflight step before calling section-specific getters.

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