filed_get_entity

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

No annotations exist, so description must compensate. It discloses that include_federal uses additional API credits but omits authentication requirements, rate limits, or data freshness. Behavioral traits beyond parameter cost are not described.

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 efficiently convey purpose, scope, and key constraint (ID format). No redundant or wasted words.

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?

Covers main content, ID format, and optional parameter cost. Lacks explanation of response structure or any usage restrictions (e.g., need for API key). Still sufficient for a simple retrieval tool with two parameters.

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 covers both parameters completely. Description adds value by specifying the ID format with an example and noting that include_federal incurs extra cost, which is not in the 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?

Description clearly states 'Get full details for a specific business entity' and enumerates included content (officers, agent, filing history, status). It also notes optional federal data enrichment, distinguishing it from search siblings.

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?

Provides important context on entity ID format and optional parameter cost, but no explicit guidance on when to use this tool versus siblings like filed_company_intel or the search tools.

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