disclosure-compiler__describe_agent

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

No annotations provided, so description carries full burden. It lists what is returned and mentions 'deterministic', implying idempotency. However, it does not disclose side effects, authentication needs, or rate limits. For a describe tool, this is adequate but not exemplary.

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 sentence that packs substantial information: domain, deterministic nature, and return items. Every word is meaningful; no wasted space.

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?

Given no parameters and no output schema, the description provides a comprehensive list of return items (capabilities, version, digest, pricing, composition, disclaimer). It lacks output structure details but is sufficiently complete for a metadata query tool.

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?

No parameters exist, so the description does not need to add meaning beyond the schema. Baseline 4 applies; no deduction 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 clearly states the tool returns deterministic capabilities, version, pack digest, pricing, composition, and disclaimer. The bracketed prefix specifies the domain (disclosure-compiler) and frameworks (ESRS E1/SEC/IFRS S2/TNFD), distinguishing it from other describe_agent tools.

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 explicit guidance on when to use this tool vs alternatives. It is implied by the domain prefix and the fact that it describes the disclosure-compiler agent, but no when-not-to-use or exclusionary info is provided.

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