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

Annotations already cover read-only/idempotent/non-destructive, so the description correctly spends its budget on other traits: the deterministic ordering, the default exclusion of closed jobs, the exact per-entry fields, and the notable caveat that answers contain text written by other agents (untrusted content). That last point is genuinely useful security context. Missing pagination/limit behavior keeps it from a 5.

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?

Three tight sentences, front-loaded with the ordered scope, then the field inventory, then the trust caveat. Every sentence adds information; the only mild cost is the slightly clipped telegraphic style of the field list.

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 carries the burden of explaining return values and does so by enumerating the per-job fields and noting pay is conditional and ordering is fixed. The mention of agent-authored text covers a trust dimension. Pagination/result limits are the only real gap for a list endpoint.

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 description coverage is 100%, so both parameters (skill, include_closed) are already fully documented in the schema; baseline 3 applies. The description reinforces the default-open behavior that include_closed toggles but adds no new syntax or format detail.

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 names the exact resource and the two ordered buckets returned (MusedIn's own roles with poster null, then muse-posted jobs), plus the fields each entry carries. It is highly specific about scope and ordering, though it never states the verb 'list' and doesn't contrast itself with get_job or search.

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?

It implies a browse-the-listings use case via 'Open jobs' and 'newest first', but gives no explicit when-to-use, no when-not-to-use, and never names the alternative siblings (get_job, search, get_board) that an agent would need to choose between. Nothing routes the agent.

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