list_applications

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

With no annotations provided, the description carries the full burden. It discloses that status matching is case-sensitive and exact, that returned fields depend on a configurable schema, and clarifies which statuses are server-driven versus manual edits. It explains what gets returned (job_id plus tool-populated fields) and the read-only nature of the operation, providing good behavioral context beyond the minimal schema.

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 front-loaded with the core purpose in the first sentence, then parameter details, then return-value context. It's reasonably compact for the information conveyed, though the return-fields paragraph is slightly verbose with the documentation reference. No wasted sentences; each paragraph earns its place.

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 single-optional-parameter read tool with no annotations, the description covers purpose, filter semantics, return shape (with reference to a configurable schema), and data provenance. An output schema exists to document return structure. It's complete enough for an agent to invoke confidently, though it could note error cases or pagination behavior.

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 0%, so the description must carry all parameter meaning. It thoroughly explains the 'status' parameter: exact-match semantics, case-sensitivity, example values, and behavior when omitted. The key insight that filtering requires exact tracking-store values is genuinely useful and not derivable from the bare schema.

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 'lists tracked jobs from the configured tracking store (Notion)', specifying the verb (list), resource (tracked jobs), and source (Notion tracking store). It distinguishes from siblings by clarifying it reads tracked applications rather than matching or pushing jobs, though it doesn't explicitly name the sibling alternatives.

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 provides clear usage context: the optional 'status' filter for exact matches, instructions to omit it to return all rows, and a warning that certain statuses are manual edits made in Notion rather than server-driven. It gives practical when-to-use guidance via the filter semantics, though it doesn't explicitly state when to use a sibling tool instead.

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