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

Annotations already carry readOnlyHint/idempotentHint/openWorldHint=false, so the safety profile is covered. The description still adds real behavior beyond them: unapproved listings are excluded from results, the Pro-tier gating, and the projected return fields. It omits pagination/result-size behavior despite limit and offset existing.

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?

It is short and front-loaded, but the trailing clause 'keyword: title, company, location, posted date and where to apply' reads ambiguously — it is easy to parse the colon list as additional filter parameters rather than the fields returned. That structural ambiguity costs a point.

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?

With no output schema, the description usefully names the returned fields, which is genuinely helpful. However, for a paginated list tool with limit/offset, there is no guidance on result volume, defaults, or paging, leaving a noticeable gap.

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 60% (limit and offset have no descriptions anywhere), and the description mentions only company, location, and keyword, which the schema already documents in more detail. It adds no format or syntax beyond the schema, so it lands at the baseline for partial 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?

States a clear resource (open roles at approved FirmLedger companies) and the filtering axes, and the 'approved companies only' restriction meaningfully scopes it against siblings like search_listings or get_listing. It stops short of explicitly differentiating itself from those siblings in the text.

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 enumerates what can be filtered but never says when to choose this tool over search_listings or get_listing, nor any when-not condition. Usage is only implied by the word 'jobs'.

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