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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does add useful context: the tool returns jobs in reverse chronological order ('newest first') and includes status and progress fields. However, it omits other behavioral details such as authorization requirements, pagination behavior, and how the limit parameter affects results. The description is not misleading, but it is minimal.

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 that immediately communicates the action, target, and key details. Every word contributes to understanding the tool's purpose. There is no fluff or unnecessary information.

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?

For a simple listing tool with one optional parameter and no output schema, the description covers the core functionality but leaves gaps. It mentions the output includes status and progress but does not describe the full response structure or how the limit parameter works. Since no output schema exists, the description should provide more detail about the return format, but it is adequate for a basic understanding.

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?

The schema has one parameter (limit) with a default of 50, but the description does not mention it at all. Schema description coverage is 0%, so the description was expected to compensate, but it fails to explain what 'limit' means or how it affects the output. The parameter is simple, but the description adds zero value beyond the schema itself.

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's function: listing the user's ingest jobs, with specific details on ordering (newest first) and included information (status and progress). It distinguishes itself from sibling tools like brainkb_job_status (which likely targets a single job) by explicitly saying 'jobs' and specifying 'ingest jobs'.

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 the use case (listing ingest jobs) but gives no explicit guidance on when to use this tool versus alternatives like brainkb_job_status. It doesn't mention exclusions, prerequisites, or when a different tool would be more appropriate. The context is clear but not fully articulated.

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