get_constitution

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

Without annotations, the description minimally implies a read operation but does not disclose behavioral traits such as authentication requirements, error handling for missing persona, or whether the merge includes all rules. More detail is needed for safe invocation.

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, front-loaded sentence that efficiently conveys the tool's purpose. It is concise with no superfluous information, though it could be slightly more structured.

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 simple read tool with one documented parameter and no output schema, the description adequately outlines the return content (merged constitution with rules and UVC qualities). However, it omits details like output format or the relationship to sibling tools, which could be helpful.

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 single parameter 'persona_id' is already fully documented in the schema with a default and description. The tool description adds no additional semantic context beyond what the schema provides, resulting in a baseline score.

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 retrieves the merged constitution for a specific persona, including active rules and UVC qualities. However, it does not differentiate from sibling tools like 'get_constitution_by_id' and 'get_uvc_qualities', which could cause confusion.

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 guidance is provided on when to use this tool versus alternatives like 'get_constitution_by_id' or 'get_uvc_qualities'. There is no context for prerequisites or exclusions.

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