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

With no annotations, the description carries the full behavioral burden. It does state the primary behavior (returns a manifest) and there are no parameters, side effects, or authorization requirements to disclose. However, it does not explicitly state that the call is read-only or what the manifest actually contains, which leaves some ambiguity about the exact result an agent should expect.

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 concise sentence with no filler. It is slightly under-specified ('this self-describing tool manifest' is ambiguous), so it does not reach the 5 level, but it is appropriately short and front-loaded.

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 tool, the description is reasonably complete, but since there is no output schema, the agent needs to know what 'manifest' means in terms of contents and format. The description does not specify that it lists the available MANDATE tools or what shape the manifest takes, leaving the return value somewhat underspecified.

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 takes zero parameters, so the schema fully covers all inputs. Per the rubric, 0 params earns a baseline of 4; the description adds nothing about parameters, but nothing is 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 states a specific action (Returns) and object (self-describing tool manifest), which clearly indicates an introspection/discovery tool rather than an action tool like mandate.mint or mandate.authorize-action. The title 'Discover MANDATE agent tools' adds context, but the description alone is slightly vague because 'this self-describing tool manifest' could be read as returning a description of only this tool rather than the full tool suite.

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 about when to call this tool versus its siblings. There is no explicit statement like 'Use to discover available MANDATE tools before calling other mandate functions.' The discovery use case is only implied by the title and name, not explained in the description.

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