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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds useful context by listing the output fields and explaining the 'latest' feed behavior. However, it doesn't disclose potential pagination limits, error handling, or any special side effects beyond the schema.

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?

Two sentences, front-loaded with purpose, then usage. No filler words. Every sentence adds value: one defines the resource and its content, the other explains the parameter modes. Excellent structure.

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?

The tool is simple with only two parameters, a complete schema, and comprehensive annotations. The description covers what the data contains, how to query it, and the two ways to use it. No output schema exists, but the description lists the key fields, making it complete enough for an agent.

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?

Schema description coverage is 100%, so both parameters are already documented. The description adds helpful guidance about CIK versus ticker for private issuers and the default limits, but it largely restates what the schema already provides. A baseline of 3 is appropriate.

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 parses Form D notices and lists the key data elements (issuer, jurisdiction, industry, amount, exemption, etc.). It distinguishes itself from generic filing tools by focusing specifically on private placement filings under Regulation D.

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 gives explicit instructions on how to use the tool: pass a CIK, ticker, or 'latest' for a market-wide feed. It also explains the context (private placements under Reg D). It doesn't mention exclusions or compare directly with siblings, but usage context is clear.

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