getCrowdfundingCampaignsByCIK

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

Annotations already provide readOnlyHint, idempotentHint, and openWorldHint, which cover safety and idempotency. The description adds no further behavioral context (e.g., no mention of data freshness, rate limits, or what 'detailed information' means). It is consistent with annotations.

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, achieving the goal without extra words. Could be slightly more structured (e.g., listing details), but it is efficient 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?

Given no output schema, the description is vague about what 'detailed information' includes. It provides minimal completeness for a simple lookup tool, but more detail on return fields would improve utility.

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 coverage is 100% with a description for the 'cik' parameter. The description adds no additional semantic meaning beyond what the schema provides; it repeats the concept of CIK but does not explain format or valid values.

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 accesses detailed information on crowdfunding campaigns for a specific company by CIK. It uses a specific verb and resource, and differentiates from sibling tools like getLatestCrowdfundingCampaigns and searchCrowdfundingCampaigns by focusing on a specific company identified by CIK.

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 implies usage when one knows a CIK number, but it does not explicitly state when to use this tool versus alternatives. No guidance on when not to use it or mention of alternatives.

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