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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety traits are covered. The description adds useful scope behavior — companies "the Saldeo user can see" — and lists the returned fields, including the critical COMPANY_PROGRAM_ID dependency.

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 compact and front-loaded: it leads with what is listed, then key returned fields, then "Start here," then the underlying endpoint. Every sentence carries useful routing or output 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 read-only listing tool, the description supplies the essential output fields and the dependency signal around COMPANY_PROGRAM_ID. Pagination details are handled by the schema, and no output schema is needed given the explicit field list.

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 the limit and offset parameters are already fully documented in the schema. The description does not add further parameter meaning beyond the schema baseline.

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 specific verb and resource — list companies/clients visible to the Saldeo user — and explains the key returned identifier, COMPANY_PROGRAM_ID, which is needed by every other tool. This distinguishes it from sibling tools and makes the tool's role unmistakable.

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 phrase "Start here" gives explicit first-step guidance, and "needed by every other tool" clarifies why an agent should call this before dependent tools. It does not name alternatives or exclusions, but there is no directly competing company-listing sibling.

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