getCompanyNotes

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

Annotations (readOnlyHint, idempotentHint, openWorldHint) already indicate a safe, idempotent read operation. Description adds 'detailed information' but does not provide additional behavioral context such as rate limits, data freshness, or any side effects. With annotations present, the description adds only marginal value.

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 containing only essential information. Front-loaded with verb and resource. No unnecessary words or repetition.

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 the single parameter and read-only nature, the description adequately covers the tool's purpose and example outputs. However, it lacks details on return structure (e.g., array or object), pagination, or whether all notes or only active ones are returned. Output schema is absent, so description could provide a bit more structure, but overall sufficient.

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% for the single parameter 'symbol', which is already described as 'Stock symbol'. The description mentions 'stock symbol' as part of the data but does not add new meaning or constraints. Baseline is 3 due to high schema coverage.

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?

Description clearly states the tool retrieves detailed information about company-issued notes, lists specific data fields (CIK, symbol, title, exchange), and uses a specific verb 'Retrieve'. It distinguishes itself from sibling tools like getCompanyProfile which are about company profiles, not notes.

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 on when to use this tool versus alternatives. Description does not mention when not to use it or provide comparisons to similar tools. Agent must infer context from the name and siblings.

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