list_okr_progress_records

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

No annotations are provided, so the description fully carries the burden. It discloses that the tool internally calls get_okrs and extracts IDs, which is a significant behavioral trait. This transparency helps the agent understand performance and dependencies.

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 two sentences, front-loaded with the purpose. The first sentence contains technical version info, but overall it is clear and efficient.

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?

The description explains the extraction of progress_record IDs with target_id and target_type, giving a sense of output. Lacks formal output schema or pagination details, but sufficient for understanding the tool's role.

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 100% (both parameters documented). The description adds value by noting that user_id_type is a pass-through to get_okrs, providing context beyond the schema. Baseline 3 is elevated to 4 due to this added context.

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 progress records for an OKR, explaining the implementation as a composite of get_okrs to extract IDs. This is specific and distinguishes it from other OKR tools.

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?

Provides clear context about the tool's limitation: it only extracts IDs and mentions the need for a separate tool (progressRecord.get) for full content. Does not explicitly compare with siblings like create_okr_progress_record, but the note helps the agent decide.

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