get_thoughts

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it indicates this is a retrieval operation, it doesn't describe what 'recorded thoughts' means, whether there are access restrictions, pagination behavior, rate limits, or what format the thoughts are returned in. The description provides basic functionality but lacks important operational context.

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 appropriately concise with three sentences that each add value: stating the core purpose, mentioning filtering capability, and describing organization option. It's front-loaded with the main purpose first. No wasted words, though it could be slightly more structured.

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 no annotations and no output schema, the description should do more to compensate. While it covers basic functionality, it doesn't explain what 'thoughts' are in this context, how they're structured, whether there are limitations on retrieval, or what the return format looks like. For a retrieval tool with zero annotation coverage, this leaves significant gaps.

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 schema already documents both parameters thoroughly. The description adds marginal value by mentioning 'optionally filtered by category' and 'organize them hierarchically by depth', which aligns with but doesn't expand beyond the schema's parameter descriptions. Baseline 3 is appropriate when schema does the heavy lifting.

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's purpose: 'Retrieve recorded thoughts' with the verb 'retrieve' and resource 'recorded thoughts'. It distinguishes from siblings like 'clear_thoughts' (deletion) and 'think' (creation), but doesn't explicitly differentiate from 'get_thought_stats' which might provide aggregated data rather than the thoughts themselves.

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 implies usage through optional filtering parameters ('optionally filtered by category', 'organize them hierarchically'), but provides no explicit guidance on when to use this tool versus alternatives like 'get_thought_stats' or 'detect_thinking_directive'. No when-not-to-use scenarios or prerequisites are mentioned.

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