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

Beyond the read-only/idempotent annotations, the description discloses meaningful behavior: the briefing is assembled raw from workspace records, not summarised; confidential memories are deliberately excluded; Wiki content appears only as titles and IDs. This gives an agent accurate expectations about output nature and limitations.

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 front-loaded with the core purpose and immediately states the primary usage rule. It is somewhat longer than strictly necessary, with motivational context about shared memory, but each sentence carries practical information about content, confidentiality, or related tools.

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 tool with no output schema, the description adequately explains what the returned briefing contains, its format, its limitations, and how to follow up. Combined with the fully described input schema and safety annotations, nothing essential is missing for correct invocation and interpretation.

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 baseline is 3. The description does not add parameter-level meaning beyond what the schema already provides for project_id and max_items, but it also does not need to since both parameters are fully documented in the schema.

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 a specific verb and resource: 'Returns everything this project knows about itself as one markdown briefing', and enumerates the exact contents (decisions, conventions, Wiki, risks, work in flight). This clearly distinguishes it from siblings like get_project_alerts or get_project_structure.

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?

It gives explicit when-to-use guidance: 'READ THIS FIRST, before you touch the project's code or answer a question about it.' It also names alternatives and conditions: call get_document_full_content for relevant Wiki documents, and save new knowledge with save_classified_memory. No usage question is left to inference.

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