Disclosure detail

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

Beyond the readOnlyHint annotation, the description discloses that published disclosures are immutable and cached permanently, that the tool is metadata-only (no file bytes), and that repeated calls cost nothing upstream. This significantly enriches the behavioral model.

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 front-loaded with a clear purpose sentence, then logically progresses to parameter semantics, usage alternatives, and caching behavior. Every sentence adds value; there is no fluff or redundancy.

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?

It covers the input provenance, return content, pagination, caching, immutability, and a clear note that file content requires resources/read. Even with an output schema present, this description leaves no relevant gap for an AI agent to select and invoke the tool correctly.

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 description coverage, but the description defines edge_no as the 32-character hex ID from search_disclosures and explains max_files with default (20) and max (100), plus the truncation behavior. This fully compensates for the bare schema.

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 starts with a specific verb+resource: 'Get one disclosure's details and attachment links by its edge_no.' It clearly scopes the tool to retrieving a single disclosure by ID, which distinguishes it from the search siblings (e.g., search_disclosures, search_disclosure_fulltext).

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?

It explicitly tells the caller where to obtain edge_no (from search_disclosures) and when to use resources/read instead for file contents. It also gives guidance on handling truncation by increasing max_files, which is actionable usage context.

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