get_okrs

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

No annotations provided, but description discloses batch nature (max 10 IDs) and response content. Lacks explicit statement that it is a read-only operation and does not cover rate limits or error handling. Still adds useful behavioral context beyond 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?

Single sentence efficiently conveys core purpose and constraints. No redundant 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?

With no output schema, description compensates by listing fields returned (objectives, key results, progress, alignments). Missing details on response structure or error handling, but adequate for a fetch-by-id tool.

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 covers 100% of parameters and each parameter has a description. Tool description does not add extra meaning beyond what schema already provides (e.g., source of IDs from list_user_okrs is in schema). Baseline of 3 is appropriate.

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?

Description clearly states verb 'Batch-fetch' and resource 'full OKR details' with specifics on content (objectives, key results, progress, alignments). Contextually distinguishes from sibling list_user_okrs which lists OKRs but not full details.

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?

Description implies usage when OKR IDs are available ('by OKR IDs') and mentions it's a batch operation. However, it does not explicitly state when to use vs alternatives like list_user_okrs or provide when-not-to-use guidance.

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