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. It includes only a cryptic tagline and does not disclose any behavioral traits such as whether the tool is read-only, requires authentication, or has side effects. This is insufficient for an agent to understand the tool's behavior.

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 extremely short (one sentence), but it sacrifices clarity for brevity. It is under-specified rather than effectively concise, leaving the agent guessing about the tool's function.

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?

With no parameters, no output schema, and no annotations, the description is critically incomplete. It does not explain what the tool returns, how it works, or any details about the agent description. A minimal self-description tool still requires clarity on what 'self-description' entails.

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?

There are no parameters, so the input schema is trivially covered (100%). The description adds no additional meaning beyond the schema, but the baseline for high coverage is 3. The tool gains no credit for parameter explanation because there are none.

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 is vague and does not explicitly state what the tool does. It mentions 'covenant — deny-by-default authority leases' as a contextual header but fails to clarify that this tool describes the agent's identity or capabilities. Without more detail, the purpose is unclear.

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?

The description provides no guidance on when to use this tool versus the many other describe_agent tools in different namespaces (e.g., identity__describe_agent, trust__describe_agent). There are no usage conditions, prerequisites, or alternatives mentioned.

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