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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is fully covered. The description adds one piece of real context — that approval requirements are org-configurable and business workflow approvals always apply — plus the connected-organization scoping, but it doesn't explain pagination behavior or what happens if the project has no notes.

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?

Only three sentences, but two of them are generic template copy (organization scoping and approval policy) while the operationally important sentence, "Read a project's notes," sits in the middle. The content that matters is not front-loaded.

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?

An output schema exists and annotations are rich, so return values and safety need not be restated. However, for a 4-parameter tool with zero schema documentation, the description leaves the id-vs-projectId question and pagination semantics entirely unresolved, which is the main thing an agent needs before calling it.

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 0%, so the description must carry the burden and it does not. Most notably it never clarifies the ambiguous coexistence of `id` and `projectId` in a tool named list_project_notes, nor does it explain limit/offset pagination (defaults 50/0, max 100).

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?

"Read a project's notes" names a specific resource and a read operation, and the tool name plus title reinforce it. It does not distinguish the tool from nearby siblings such as list_project_documents or update_project_note, so an agent has to infer the boundary from naming conventions alone.

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?

"Use this when working with RetailHardHat projects records in the connected organization" is scope boilerplate, not a usage rule — it never says when to choose this over listing tasks/documents or when notes are unavailable. No exclusions or alternatives are mentioned, so the agent gets no routing signal.

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