get_thinking_profile

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

Discloses file source and fallback behavior, but no annotations are provided. Lacks information about permissions, caching, or output format. Behavior is adequately, not richly, described.

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?

Two sentences, front-loaded with the primary action. No wasted words. Every sentence provides essential 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 tool with no parameters and an output schema, the description covers source, location, and missing-file behavior. Complements the schema effectively.

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?

No parameters exist, and schema coverage is 100%. The description adds value beyond schema by specifying the file path and defaulting behavior, which contextualizes the zero-parameter call.

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 'Read and return the current thinking profile' with a specific file path, distinguishing it from sibling tools like update_thinking_profile that write. The verb-resource pair is precise.

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?

Implied usage from name and context, but no explicit guidance on when to use versus alternatives like get_working_memory or compare_profiles. No exclusions or conditional scenarios described.

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