Retrieve All Notes In The Project

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

Annotations correctly indicate a read-only operation, but the description misrepresents the output as 'Bid Board records' instead of notes, undermining transparency about what the tool actually returns.

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 short but includes misleading sentences that contradict the tool name and endpoint, reducing conciseness and clarity. Every sentence should be accurate and necessary.

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 output schema, the description should accurately describe the return type. It incorrectly states 'Bid Board records' instead of notes, and provides no detail on the note structure, leaving the agent with incomplete and wrong information.

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%, and the description adds context about pagination control and required parameters. However, it does not add significant meaning beyond the schema (e.g., defaults are not repeated).

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 states 'Retrieve all notes in the project', which is clear, but then contradicts itself by saying 'fetch the full details of a specific Bid Board records', causing confusion about whether it returns one record or many and what resource is actually retrieved.

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 provides misleading usage guidance ('specific Bid Board records') and does not differentiate from sibling tools like retrieve_a_note_by_id_in_the_project_company_v2_0. No when-not-to-use or alternatives are mentioned.

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