fiken_list_offer_drafts

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states 'List offer drafts' and does not reveal pagination behavior, data freshness, error handling, or what happens when no drafts exist. The schema provides pagination details, but the description adds no value beyond that.

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 extremely concise at four words, and the purpose is stated upfront. However, while brief, it could benefit from additional context to improve other dimensions, making it a 4 rather than a 5.

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?

Despite the tool's simplicity, the description lacks completeness. There is no output schema, and the description does not specify that the tool returns a list of offer draft objects or any details about the response format. An agent would need to infer this from context.

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?

All three parameters have descriptions in the schema (100% coverage), so the baseline is 3. The description does not add any additional meaning beyond the schema, as it simply reiterates 'for a company' which is already implied by the companySlug parameter.

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 it lists offer drafts for a company, using a specific verb and resource. However, it does not explicitly distinguish from sibling tools like 'fiken_list_offers' (which presumably lists confirmed offers), leaving the differentiation implicit.

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 is provided on when to use this tool versus alternatives such as 'fiken_get_offer_draft' or 'fiken_list_offers'. The only cross-reference is in the companySlug parameter description pointing to 'fiken_list_companies', but there is no broader usage context.

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