Governance Sessions

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

The description says 'List' and 'Returns session files with full data,' which signals a read/retrieval operation and provides some return-behavior context. However, there are no annotations such as readOnlyHint or destructiveHint, and the description does not address authentication, rate limits, or side effects. It is adequate but not fully transparent.

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 short and front-loaded with the listing purpose, which is good. However, it is repetitive: 'Returns session files with full data' is echoed almost verbatim in 'Returns: Dict with governance session list.' The second return statement adds little and could be removed or merged.

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?

This is a simple zero-parameter list operation with an output schema present, so the description does not need to explain return values in depth. It covers the subject matter ('governance simulation sessions') and the data scope ('full data'). It is incomplete only in not addressing the likely ambiguity with civitae_meetings.

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 input schema has zero parameters and schema description coverage is 100%, so there are no parameter semantics for the description to clarify. Per the rubric, a zero-parameter tool receives a baseline of 4. The description adds nothing about parameters, but none are 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 uses a specific verb and resource: 'List governance simulation sessions (committee and Robert's Rules).' This clearly identifies what the tool does. However, it does not distinguish itself from the sibling tool civitae_meetings, so an agent may struggle to choose between 'sessions' and 'meetings' without further context.

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 about when to use this tool versus alternatives. It does not mention civitae_meetings or any other sibling, nor does it state any conditions, exclusions, or prerequisites. The agent must infer usage solely from the tool name and description.

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