workboard_get_my_objectives_tool

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

No annotations provided; description states it retrieves objectives via auto-discovery, but does not detail potential side effects or edge cases (e.g., empty results, auth enforcement). Adequate but could be more explicit.

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?

Very concise: three short sentences front-load purpose and include critical usage guidance. No unnecessary words.

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?

Given the simple tool (1 optional param, output schema exists), description provides enough context for an agent to select and use it correctly. Minor gap: no mention of authentication context, but implied by 'authenticated user'.

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 the single parameter at 100%; description adds value by explaining the auto-discovery behavior when parameter is omitted, which aids correct invocation.

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 it retrieves the current user's objectives with key results, distinguishing it from sibling tools like workboard_get_objectives_tool by emphasizing automatic user determination and no ID requirement.

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?

Explicitly recommends use when users ask about 'my objectives' or 'my OKRs', implying alternatives for other cases. It also explains the key benefit: no IDs needed.

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