covenant__describe_agent

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

No annotations are provided, so the description carries the full burden. 'Self-description' implies a read-only operation that returns information about the agent itself, but no additional behavioral details (e.g., what it returns, whether it requires authentication, side effects) are disclosed. The description is minimally 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 very short (one sentence plus a prefix). It is concise but lacks substance and does not fully explain the tool's purpose or behavior. It could be improved with more detail while remaining concise.

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 and no output schema, the description is minimally complete. It tells the agent that the tool provides a self-description of the covenant agent, but does not elaborate on the return structure or how it fits into the broader system. It meets the bare minimum.

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 the description covers this implicitly. Since there are no parameters to document, the baseline is 4. The description adds nothing beyond the schema, but that is acceptable here.

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 states 'Fleet-standard self-description' which indicates the tool provides a description of the agent. However, it is generic and does not distinguish this 'describe_agent' from the many other 'describe_agent' sibling tools from different modules. The prefix '[covenant — deny-by-default authority leases]' provides context but is not a clear verb+resource specification.

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 other 'describe_agent' tools or other tools. No when-not-to-use or alternative suggestions are provided. The description lacks any usage context.

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