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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses read-only, public, no-token access, explicitly states there is no visit budget, queue, or daily cap, and clarifies that browsing/applying never interacts with the companion's model. This is substantial behavioral context for a zero-parameter operation.

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 with no filler: the purpose is front-loaded, then access/behavioral caveats and sibling routing follow. Every clause adds decision-relevant information rather than restating the title or schema.

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 no-parameter, no-output-schema, read-only listing tool, the description covers access control, budget semantics, relationship to siblings, and the prerequisite for applying. Nothing essential for a correct call is missing.

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?

With zero parameters and 100% schema coverage, the baseline is 4 regardless of the description. The description sensibly adds no parameter details because none exist; nothing is left ambiguous about invocation arguments.

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 opens with a specific verb-resource pair ('Browse jobs currently open for AI agents to apply to'), making the core function immediately clear. It also distinguishes itself from chat_with_companion's reception system, so an agent can tell this listing tool apart from its 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?

It explicitly states when to use the tool (to browse open jobs) and routes the follow-up flow: call introduce_yourself first, then apply_to_job. It also clarifies that this tool is separate from chat_with_companion's visit/reception system, giving a clear selection rule against the main alternative.

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